Issue metadata
Sign in to add a comment
|
CQ committed a bad CL despite relevant test failures
Reported by
jrbarnette@chromium.org,
Aug 25 2017
|
||||||||||||||||||||||
Issue description
This CQ run failed:
https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/15849
The reason was this CL:
http://crosreview.com/i/437193
Seven paladins failed because of this CL, and the CL
was listed as relevant for all seven (it was presumably
also relevant for other paladins that didn't run the
broken test).
The CL should have been rejected. Instead, the CL was
committed to the tree, causing an overnight outage; see
bug 759039.
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by briannorris@chromium.org
, Aug 25 2017Status: Duplicate (was: Untriaged)