https://uberchromegw.corp.google.com/i/chromeos/builders/tricky-chrome-pfq/builds/3293
https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Ftricky-chrome-pfq%2F3293%2F%2B%2Frecipes%2Fsteps%2FTestSimpleChromeWorkflow%2F0%2Fstdout
[32567/36222] CXX obj/third_party/WebKit/Source/core/dom/dom_3/StyleChangeReason.o
[32568/36222] CXX obj/third_party/WebKit/Source/core/dom/dom_3/TagCollection.o
[1;31m11:43:08: ERROR: Timeout occurred- waited 21033 seconds, failing. Timeout reason: This build has reached the timeout deadline set by the master. Either this stage or a previous one took too long (see stage timing historical summary in ReportStage) or the build failed to start on time.[0m
[1;31m11:43:08: ERROR: Timeout occurred- waited 20829 seconds, failing. Timeout reason: This build has reached the timeout deadline set by the master. Either this stage or a previous one took too long (see stage timing historical summary in ReportStage) or the build failed to start on time.[0m
Just figured this out, but filing bug anyway for the record...
xixuan - the failed build took 2 hour at stage BuildReexecutionFinished
xixuan - in the log of BuildReexecutionFinished, I see some swarming command failed and retried
Root cause is HWTest swarming failures, issue 720005
