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 <boyuanz@xxxxxxxxxx> 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 <iemejia@xxxxxxxxx> wrote:
>> It seems that Beam snapshots are broken since Dec. 2
>> It seems "The :beam-website:startDockerContainer task failed."
>> Can somebody please take a look.