This is a failure in just the precommit for #2636, nothing that has been
committed yet. It wouldn't affect other builds.
On Sat, Apr 22, 2017 at 9:42 AM, Ted Yu wrote:
> Looks like this might be the cause for the failed build (
> https://builds.apache.org/view/Beam/job/beam_PreCommit_
> Java_Mav
They did kill a couple of builds that were running, but the builds that
started immediately after suffered the same hanging.
Now it seems builds aren't being started at all for new pushes to PRs. And
invoking 'Retest this please' seems to do nothing as well.
On Mon, Apr 24, 2017 at 8:53 AM Jean-Ba
>
> 1. Have people unassign themselves from issues they're not actively
> working on.
> 2. Have the community engage more in triage, improving tickets
> descriptions and raising concerns.
> 3. Clean house - apply (2) to currently open issues (over 800). Perhaps
> some can be closed.
>
+1 on all th
Agree, it's probably due to the update and reconfiguration happening.
Regards
JB
On 04/24/2017 07:41 AM, Davor Bonaci wrote:
Intermittent hanging exist for several days, maybe up to a week. I think it
correlates with updates/restarts/reconfiguration/etc. of the Jenkins
instance on the infrastru
Intermittent hanging exist for several days, maybe up to a week. I think it
correlates with updates/restarts/reconfiguration/etc. of the Jenkins
instance on the infrastructure side. Terminating the build and restarting
did work around the problem a few times.
On Sat, Apr 22, 2017 at 9:42 AM, Ted Y
