github: What to do when unittests fail?

[Jonathan M Davis]

> On 5/24/11, Jonathan M Davis <jmdavisProg at gmx.com> wrote:
> > The tests are
> > currently fully passing on Windows.
> 
> But the thing is, the autotester uses a changeset dated May 22nd, but
> the latest changeset on github
> (https://github.com/D-Programming-Language/phobos) is May 16th, and
> that is the one I've cloned from and it has failing unittests.
> 
> So I'm not sure where to go from there.

Just grab what's on github. It's the latest. The autotester grabbed something 
from May 22nd last, because dsimcha accidentally committed some code to the 
main repository instead of his own. He reverted it. No more checkins have been 
made since then, so the autotester hasn't grabbed anything new yet. github 
always has the latest code.

Besides, if you look at the output on github, it's giving the same output as 
your original post. Note that it's a printout saying that a test is broken 
_not_ a test failure. It's a reminder that a test (and possibly related code) 
needs to be fixed. No unit tests are actually failing. An AssertError is 
thrown whenever that happens. What's on github is fine.

- Jonathan M Davis