Issue metadata
Sign in to add a comment
|
Wrongly blame 498253 -- TIMED_OUT -> test not exist |
||||||||||||||||||||||||
Issue descriptionDetail is https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vYTI2YzBjMWM5ZTE2NDAyYWU5NzRkZmE5N2U1ODA2ODdjMmM3YjIzZQw CL almost certainly could not have caused this regression.
,
Sep 7 2017
Bumping pri.
,
Sep 7 2017
Jeff: is the CL ready to land?
,
Sep 7 2017
,
Sep 7 2017
The CL has landed but the version with the fix has not been set to default, the original tracking bug should be issue 700980
,
Sep 7 2017
,
Sep 8 2017
This is a 2-part fix, the other is documented in issue 763124 The first part was the error was originally undetected, which would then pass the swarming task along as though everything's fine but an error actually occurred. That has been resolved in issue 700980 . However due to recent refactoring, subsequent pipelines are now ignoring the now-detected error and attempting to create a data point out of an invalid swarming task, which is addressed in issue 763124 |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by mthiesse@chromium.org
, Sep 5 2017