Clobbering right before compilation in compile.py has a bunch of issues (it tends to delete files that were created by earlier steps and that are needed for compiles).
I fixed this for recipe-using bots in bug 574557 , but the recipe_autogen.py recipe files don't use the normal recipe machinery for some reason (https://cs.chromium.org/search/?q=file:recipe_autogen+clobber+-file:%5C.json&sq=package:chromium&type=cs).
Instead of passing --clobber to compile.py, they should use chromium_apply_configs: ['clobber'] and call chromium.api.runhooks() which will then automatically add a clobber step. (If that's infeasible, then this line https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/chromium/api.py?rcl=0&l=494 should be extracted into its own "clobber()" function and then the recipe should call chromium.api.clobber() before runhooks).
I'm not sure what the overall vision for these generated recipe bots is, so giving this to you rather than doing it myself.
Without this, swarming doesn't work on clobber gn bots (since the clobber-during-compile step deletes the .isolated files gn creates during runhooks), so this blocks gn.
Comment 1 by estaab@chromium.org
, Jun 7 2016Owner: ----
Status: Available (was: Assigned)