On 2/6/2017 11:37 AM, RjOllos wrote: > > > On Sunday, February 5, 2017 at 1:59:02 PM UTC-8, RjOllos wrote: > > > > On Saturday, February 4, 2017 at 2:50:23 AM UTC-8, cboos wrote: > > Hi, > > It seems all the recent Travis builds are marked as in "error" > for no > good reasons. Only the Linux builds, the MacOS ones are fine. > From the > logs, all seems fine, there seem to be no actual errors. > > Anyone has an idea? > > -- Christian > > > Running a build that previously succeeded fails, so it's probably > due to a change in the TravisCI platform or one of our dependencies. > I tried clearing the package cache and rerunning a build, but that > doesn't help. It seems to be failing on every branch. > > - Ryan > > > It seems to be fixed now. If the problem "fixed itself", then it might > be explained by: > > https://www.traviscistatus.com/ > > The container-based Linux infrastructure requires emergency > maintenance to ensure all instances are running a known working > version of the "worker" component. We had started rolling out a > newer version this past Thursday, then began rolling back due to > reports of mismatched exit code and job status. Please expect > partial capacity behavior similar to times of high load during the > maintenance, which we expect will take between 1-2 hours. >
That sounds like it! Indeed, the exit status was clearly reported to be 0, but the job status was set to "failed". I've added a link to this status page in the wiki page. https://trac.edgewall.org/wiki/TracDev/AutomaticBuilds#Troubleshooting Thanks for investigating! -- Christian -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
