Thanks Łukasz for adressing this! In my opinion, such builds are de facto failed and should be treated in the same way. I think it's fine for now to notify builds@, but in the future we should also take this problem into account when developing an anomaly detection system. I left some comments on the solution in jira.
Kamil On Thu, Oct 17, 2019 at 12:54 PM Łukasz Gajowy <[email protected]> wrote: > Hi all, > > I created BEAM-8422 <https://issues.apache.org/jira/browse/BEAM-8422> because > I think that we should notify builds@ even when a job timeouts. It seems > not to be the case right now and we have 5 constantly timeouting jobs which > is invisible for people relying on builds@ (see more in the issue). > > I also created a PR <https://github.com/apache/beam/pull/9816> for this > (looking for reviewers, btw). It's a "draft pr" now - I will mark it as > ready in a few days if there's general agreement on the devlist. :) > > Thank you! > Łukasz >
