Branko Čibej wrote:
> Bert Huijben wrote:
>
>> Recently the test framework was changed to support work-in-progress
>> tests. When this support was completed the Windows buildbot was offline.
>>
>> Since a few days the buildbot is back online (Thanks D.J. Heap!), and
>> for the last few days the Windows tests don't report an error in the
>> summary:
>>
>> ===============
>>
>>
> [...]
>
>> =========================
>>
>> But the testresult is still failed (red) and broken builds are reported
>> to the svn-breakage list.
>>
>> If I look in the raw log file I find 'FAIL:' lines for the
>> work-in-progress patch tests, but those aren't reported in the summary
>> (Maybe because it doesn't look for 'FAIL:' lines?).
>>
>> Could somebody please look at this issue?
>>
>>
>
> Hm. I made sure that any failures reported from wimpy tests did not
> cause the tests to exit with non-zero status. Individual per-test
> results should be XPASS and XFAIL, too.
>
> IMHO buildbots should look at test exit status, not grep the log file;
> run-tests.py already does that better.
>
So it turns out that Arfrever changed those patch tests from Wimp to
SkipUnless i36564 n rand they're failing on Windows again.
Tut, tut. Do not over shoulder your code throw, my young padawan. Check
buildbots. :)
I *am* very much surprised though that those failures do not appear in
the test summary.
-- Brane
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1475199
Received on 2009-03-30 01:23:21 CEST