On Wed, Oct 21, 2009 at 10:34 AM, Joe Swatosh <joe.swatosh_at_gmail.com> wrote:
> On Wed, Oct 21, 2009 at 6:26 AM, Mark Phippard <markphip_at_gmail.com> wrote:
>> On Wed, Oct 21, 2009 at 1:36 AM, Joe Swatosh <joe.swatosh_at_gmail.com> wrote:
>>
>>> There is a Java error and failure also. I apologize for the long time
>>> that the bindings buildbot has been failing due to Ruby, and masking
>>> other potential problems. Now that the Ruby bindings are close to
>>> passing again, I hope that the Java bindings will get fixed soon, too.
>>
>
>> The failure is relatively new, and involves the diff tests. There is
>> work going on in this area and there have been failing tests in the
>> main test suite, so I suspect these are related. I have been holding
>> off looking at it until that work seems done, as I kind of expected
>> the test to start working again. Based on the assertion failure, it
>
>>
>
> I know what you mean. I was just getting excited to see a green build,
> after the Ruby bindings being the bad actor for such a long time. I
> should have realized you were tracking....
I was able to find the problem in the library and fixed it in r40148,
so the prodding was worthwhile!
I can fix the other JavaHL test by using --accept=theirs-conflict
instead of theirs-full. For the purposes of the test I was doing it
does not change anything. I worry that I am just covering up a real
error that needs to be fixed though. I am not clear as to why the
main tests are Green with this problem still in place. Every command
line user will see it when they use that accept option.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2409799
Received on 2009-10-21 16:39:03 CEST