If there's evidence that it's been happening for a while (>1 day), then I'd say open a ticket for it now.
Note that Jenkins is managed by the builds team, which is separate to the infra team. If it's reported to infra, there will just be a delay as someone will have to manually re-assign it to the correct project. Open a ticket at https://issues.apache.org/jira/browse/BUILDS and/or see the mailing list at https://mail-archives.apache.org/mod_mbox/www-builds/ Richard. On 18 August 2015 at 11:35, Aled Sage <[email protected]> wrote: > Hi all, > > It seems like @asfbot's builds are timing out for our PR branches (e.g. for > PRs #834, #831, #820, etc). > > Anyone have any ideas, or shall we raise this with Apache Infra straight > away (or has that already been done)? > > The final timeout message in the build stdout is something like: > > Waiting for Jenkins to finish collecting data > *Build timed out (after 40 minutes). Marking the build as aborted.* > channel stopped > Build was aborted > Putting comment on the pull request > Finished: ABORTED > > --- > Hadrian commented on https://github.com/apache/incubator-brooklyn/pull/829: > > I also opened a ticket for infra to look into the jenkins builds status. > > https://issues.apache.org/jira/browse/BUILDS-107 > > But that was about not being able to stop the build that had hung. > > Aled >
