Quoting Paul Burba <pburba@collab.net>:
> > -----Original Message-----
> > From: Kamesh Jayachandran
> > Sent: Monday, June 18, 2007 11:06 AM
> > To: Paul Burba
> > Cc: dev@subversion.tigris.org; D.J. Heap; Lieven Govaerts
> > Subject: Re: Buildbot failure not reported
> >
> > Paul,
> > I have fixed the failure via r25431.
>
> Kamesh,
>
> I saw that, the test still fails on Win32 though. And the builbot
> report I linked to was for r25439 (after your fix) and it reported the
> tests as passing despite the failure clearly occurring in the log.
>
> Just check out this and you'll see what I mean:
>
> http://www.mobsol.be/buildbot/win32-xp%20VS2005/builds/1779/step-Test%20
> fsfs%2Bra_local/0
>
> I also just noticed that another test is failing:
>
> FAIL: lock_tests.py 4: commit a locked file with a prop change
While the tests are indeed failing, the overview doesn't show those failures:
Running all tests in merge_tests.py [33/50]...success
..
Running all tests in lock_tests.py [45/50]...success
..
The cause must be somewhere in the test framework. I wonder, DJ, are you running
the tests in parallel?
Lieven
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 18 17:36:34 2007