RE: serf buildbot FAIL on trunk@1407545

On second thought, it is probably caused by the sylink not changing
filesize while we have wait for timestamps disabled in the testsuite.

That would exactly change this behavior on the specific buildbot.

Bert

 *From:* Bert Huijben <bert_at_qqmail.nl>
*Sent:* November 10, 2012 11:26 AM
*To:* Philip Martin <philip.martin_at_wandisco.com>,Ivan Zhakov <
ivan_at_visualsvn.com>
*CC:* dev_at_subversion.apache.org
*Subject:* RE: serf buildbot FAIL on trunk_at_1407545

This is a new test on some update of symlink behavior.

There should be a real change committed in that test, so not seeing it on
update (the reported error) indicates that there is some bug in previously
untested behavior.
(It could be an error in the test, but the testcase is not really
environment specific)

I would guess that the real error is in the commit step higher up in the
test, but we don’t verify the output there yet.

Bert

Sent from Windows Mail

 *From:* Ivan Zhakov <ivan_at_visualsvn.com>
*Sent:* November 9, 2012 9:53 PM
*To:* Philip Martin <philip.martin_at_wandisco.com>,Bert Huijben <
bert_at_qqmail.nl>
*CC:* dev_at_subversion.apache.org
*Subject:* Re: serf buildbot FAIL on trunk_at_1407545

On Fri, Nov 9, 2012 at 11:17 PM, Philip Martin
<philip.martin_at_wandisco.com> wrote:
> Philip Martin <philip.martin_at_wandisco.com> writes:
>
>> The centos buildbot failed on trunk_at_1407545. I can't reproduce it. The
>> failing update produces:
>
> It's happened a second time on trunk_at_1407583. Between the failures it
> worked on trunk_at_1407556.
>
The failing test (special_tests#25) added r1407131 (two days ago).

Bert, do you have any ideas why this test failing some sometimes?

--
Ivan Zhakov