[Findit] Failed to get step result log for build 0 which leads failures in all following analyses |
||||
Issue descriptionUrl to the build Failure: https://luci-milo.appspot.com/buildbot/chromium.memory/Linux MSan Tests/20 What is the bug or feature: 1. Analysis failed because of "ValueError: No JSON object could be decoded" error in detect_first_failure_pipeline 2. This error is because analysis of build 1 failed because of "Failed to get swarming test results for a previous build." error 3. Analysis of Build 0 succeeded but failed to get test_level data. 4. I contacted maruel@ and it turned out "buildnumber:0" tag is not set in swarming tasks of build 0 (a possible buildbot bug), which makes Findit thinks steps in build 0 are not isolated. And that caused failure in analysis of build 1 and make step.log_data to be None which caused failures in all following analyses. This error should not be common since it tends only happen on build 0, but should be easy to fix.
,
Apr 13 2017
,
Apr 13 2017
,
Apr 14 2017
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/262d4938ebaf306edf5045d454cbb3b5044dc268 commit 262d4938ebaf306edf5045d454cbb3b5044dc268 Author: Chan <chanli@chromium.org> Date: Fri Apr 14 16:54:33 2017 [Findit] Fix bugs when running analyses of builds on a new builder. Skip build 0 to avoid some unexpected failures. Bug: 711438 Change-Id: I2b1176f0635c15469cd2c5034367460af8d7c841 Reviewed-on: https://chromium-review.googlesource.com/477434 Reviewed-by: Shuotao Gao <stgao@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org> [modify] https://crrev.com/262d4938ebaf306edf5045d454cbb3b5044dc268/appengine/findit/waterfall/detect_first_failure_pipeline.py
,
Apr 14 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by st...@chromium.org
, Apr 13 2017