This was caused by a bad change landing on the waterfall in
https://codereview.chromium.org/2627093009
it was reverted in
https://codereview.chromium.org/2648383002
It looks like the problematic CL was missing an entry in gn_isolate_map.pyl, which caused analyze to fail.
However, because we changed //testing/buildbot/*.json, the recipe's whitelist of "changes we can't analyze" (//testing/buildbot/trybot_analyze_config.json) matched, and so we skipped analyze and didn't detect the bug.
I think we need to change things so that we call analyze unconditionally and fail the build if analyze fails, but if analyze succeeds, *then* check the whitelist and ignore analyze's results. This should be a simple enough change.
In addition, we should work to make sure that the whitelist is as small as possible.
See crbug.com/684060 for the bug that motivated this one :).
Comment 1 by sheriffbot@chromium.org
, Feb 12 2018Status: Untriaged (was: Available)