The builder+tester split and later swarming conversion made the following use case more complicated than what it used to be:
1. I get a CL reverted because it causes flakiness on an ASAN bot [1]
2. I open the failure link [2] to reproduce the failure
3. I read the "generate build files" output and copy/paste in my gn args.
3. is no more, because the tester tests only. It makes all sense from an infra viewpoint, but now in order to get to the GN args I have to follow the trigger and get to the builder... too long.
Would be nice if the builder did also save the the args.gn somewhere and the tester has a step which just cats that. Something of the form "this is how the builder did build the thing that i am testing here". Or any other equivalent would work really.
P.S.: I know about swarming.py reproduce, but I really want to build locally not pull prebuilts.
[1] https://chromium-review.googlesource.com/c/528513/
[2] https://build.chromium.org/p/chromium.memory/builders/Linux%20ASan%20LSan%20Tests%20%281%29/builds/36356
Comment 1 by dpranke@chromium.org
, Jun 12 2017