Beam9 is offline right now. But, the job also failed on beam4 and 13 with "Could not determine the dependencies of task ':beam-sdks-python:test.". Seems like the task dependency did not setup properly.
On Wed, Dec 12, 2018 at 2:03 AM Ismaël Mejía <ieme...@gmail.com> wrote: > You are right it seems that it was related to beam9 (wondering if it > was bad luck that it was always assigned to beam9 or we can improve > that poor balancing error). > However it failed again today against beam13 maybe this time is just a > build issue but seems related to python too. > > On Tue, Dec 11, 2018 at 7:33 PM Boyuan Zhang <boyu...@google.com> wrote: > > > > Seems like, all failed jobs are not owing to the single task failure. > There failed task were executed on beam9, which was rebooted yesterday > because python tests failed continuously. +Yifan Zou may have more useful > content here. > > > > On Tue, Dec 11, 2018 at 9:10 AM Ismaël Mejía <ieme...@gmail.com> wrote: > >> > >> It seems that Beam snapshots are broken since Dec. 2 > >> > https://builds.apache.org/view/A-D/view/Beam/job/beam_Release_Gradle_NightlySnapshot/ > >> > >> It seems "The :beam-website:startDockerContainer task failed." > >> Can somebody please take a look. >
