Issue metadata
Sign in to add a comment
|
pre-cq: BuildPackages failure marked as a lab_fail |
||||||||||||||||||||||||
Issue descriptionThis CL: https://chromium-review.googlesource.com/c/483075/ This pre-cq build: https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/31869 failed BuildPackages. The message posted on the CL says: "The build encountered Chrome OS Lab infrastructure issues. Your change will not be blamed for the failure." Looking at the sources, we seem to think this is a lab failure: http://shortn/_Na5Tpo8esv Why?
,
Apr 25 2017
,
Jun 9 2017
Issue 721910 has been merged into this issue.
,
Jun 9 2017
I noticed this again on https://chromium-review.googlesource.com/c/530084/ " NOTE: The Pre-Commit Queue will retry your change automatically. The following build(s) failed: samus-no-vmtest-pre-cq: cbuildbot failed in https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/57216 The build encountered Chrome OS Lab infrastructure issues. Your change will not be blamed for the failure. " That makes no sense, since this build doesn't touch the lab.
,
Jun 21 2017
Different symptoms caused by a same reason. merging two issues.
,
Jun 21 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nxia@chromium.org
, Apr 21 2017Owner: nxia@chromium.org