www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7983) svn-x64-ubuntu-gcc spurious failures
Date Sun, 28 Feb 2016 05:47:18 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170881#comment-15170881

Chris Lambertus commented on INFRA-7983:

Is this still a problem?

> svn-x64-ubuntu-gcc spurious failures
> ------------------------------------
>                 Key: INFRA-7983
>                 URL: https://issues.apache.org/jira/browse/INFRA-7983
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Ben Reser
>            Assignee: Chris Lambertus
> Since the buildbot upgrade the svn-x64-ubuntu-gcc builder has had spurious failures during
the update phase, always with an error about Corrupted xml.  It always happens when running
`svn info --xml` either before or after update (usually after update).  I've dug around and
this error is generated on the master when it tries to parse the XML.  Here is an example
of such a build from earlier today:
> http://ci.apache.org/builders/svn-x64-ubuntu-gcc/builds/275
> I have tried to debug this.  I do not actually run the slave host.  But I have access
to it and the user that the slave runs as (no root).  Despite much poking around I can't figure
out what the problem here is.
> Initially I suspected that the version of the buildbot software was older but rather
it's 0.8.8 just like the version running on the master.  It does happen to be Ubuntu's packaging
of this.
> It's possible there is some sort of connectivity issue, but it seems highly odd that
this always happens during the `svn info --xml` command as opposed to various random things
> Can I get someone from Infra with access to aegis to work with me to try and determine
what is going on so we can try and get this fixed.
> Thanks.

This message was sent by Atlassian JIRA

View raw message