Complex cryptic infrastructure makes it hard for developers to reproduce failures found in CI or tryserver locally. This stems from:
- Compile on builders, test failures on testers
- Failures show up on swarming collect step, hard to reason how the test framework was started
Goals:
It should be easy to reason from the test failure how to compile and repro locally. As an alternative, it should be documented how to download the build product from swarming for repro.
Rerunning the tests should work by running a test directly or through the test framework with a filter and other optional parameters (e.g. rerun counts to make flakes more likely).
Comment 1 by bugdroid1@chromium.org
, Apr 21 2016