So far looks like a few nodes that don't work, so I've taken them offline temporarily. INFRA-16974 is tracking the issue.
I think each find-flaky job has now had a successful run after the restore. On Fri, Aug 31, 2018 at 9:49 AM Sean Busbey <[email protected]> wrote: > > looks like infra, given that all but two of the branches work. let me > try taking H10 offline and see if it works on a different host. > On Fri, Aug 31, 2018 at 8:05 AM 张铎(Duo Zhang) <[email protected]> wrote: > > > > Our flaky test jobs are not in a good status after the recovery. > > > > Error when executing always post condition: > > org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: > > Required context class hudson.FilePath is missing > > > > > > And this > > > > Caused: java.io.IOException: Remote call on H10 failed > > > > > > Not sure this is a infra issue or a problem of our scripts... > > > > Sean Busbey <[email protected]> 于2018年8月31日周五 下午1:19写道： > > > > > builds it back. precommit should be working through the backlog of > > > changes while things were down. > > > On Thu, Aug 30, 2018 at 9:35 AM Sean Busbey <[email protected]> wrote: > > > > > > > > Hi folks! > > > > > > > > As background, the ASF jenkins master (what you see when you go to > > > > builds.apache.org) went down Tuesday night[1]. ASF Infra is dutifully > > > > working to restore it to full capabilities without losing information > > > > on prior builds. Their most recent estimate has a return to normal > > > > sometime tonight or early tomorrow morning. > > > > > > > > I have a few patches I'd like to still see precommit results for > > > > before they get signed off on. I was going to set up checking them > > > > with test-patch myself, but it would only be marginally more work for > > > > me to automate it. > > > > > > > > What do folks think about me doing this as a stop-gap while ASF Jenkins > > > is down? > > > > > > > > It would be on transient hosts that essentially only I had access to > > > > (and I guess my employer?). So we'd get results posted to JIRA but > > > > getting to actual logs would be a bit more of a pain. > > > > > > > > Does anyone feel strongly about me using the existing QABot JIRA > > > > credentials vs making a "I'm a placeholder QABot" account with its own > > > > credentials? > > > > > > > > [1]: https://status.apache.org/incidents/4zl6mkyrg8qt > > >
