Often I see the build failing, but on the next page there are no warnings
and no errors.
Then when you dive into the full log, it slows down the browser and there
is no obvious ctrl-f keyword to find the error ("error" yields over 100
results, and the error isn't always at the bottom). Is there a
faster/better way to do it?
There is a log about the build timing out, but I don't really know what
timed out or where to look next.
Is 120 min a long enough time? Did something recently happen? If so Can we
increase the timeout until we debug the regression?
https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/12017/
https://issues.apache.org/jira/browse/BEAM-10390
Thanks, I would appreciate any ideas :)
Alex
