On Thu, 2019-01-03 at 07:10 -0800, Allen Wittenauer wrote: > > Sling has a few hundred modules, if you have more specific info on > > which are problematic please let us know so we have a better chance > > of > > fixing that. > > I gave up and wrote a (relatively simple) pre-amble for our > jobs to shoot any long running processes that are still hanging out > in the workspace directories. Output gets logged in the console log.
(snip) The Sling builds you pasted in your email are all from the sling-org- apache-sling-distribution-it-1.8 build job. That job is configured with an elastic timeout and looking at the build trend [1] the timeout is obeyed - builds usually complete in 30 minutes and are aborted once they pass two hours. Please let us know (here or on dev@sling ) if you find any more problems and we'll try to see if this is triggered by how we use Jenkins or if we need assistance from infra. Thanks! Robert [1]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-org-apache-sling-distribution-it-1.8/buildTimeTrend
