For flakes due to CHECK, waterfall build artifacts couldn't repro until the waterfall build is a debug one instead of release.
The reason is that trybot release build has CHECK turned on, while Waterfall release build doesn't.
Possible options here:
1. Quick: detect it, and bail out or notify bugs for that.
2. More reasonable but complex: kick off try-jobs to do the work instead of Swarming tasks.
3. Hacky one: use build artifacts from tryserver to find the regression range (might not be reliable if the binary is impacted by the patch in the tryjob), and then try-job with the same config as the trybot.
For flakes due to CHECK, waterfall build artifacts couldn't repro until the waterfall build is a debug one instead of release.
The reason is that trybot release build has CHECK turned on, while Waterfall release build doesn't.
Possible options here:
1. Quick: detect it, and bail out or notify bugs for that.
2. More reasonable but complex: kick off try-jobs (use the same config as trybot) to do the work instead of Swarming tasks.
3. Hacky one: use build artifacts from tryserver to find the regression range (might not be reliable if the binary is impacted by the patch in the tryjob), and then try-job with the same config as the trybot.
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by st...@chromium.org
, Mar 29 2017