V8: Figure out which depot tools is used by auto-roller |
||||
Issue descriptionFollow up bug after issue 843917 . V8's auto-roller checks out chromium with v8: https://ci.chromium.org/buildbot/client.v8.fyi/Auto-roll%20-%20deps/ The v8-side auto-roll script is called from the V8 inside Chrome: https://logs.chromium.org/v/?s=chromium%2Fbb%2Fclient.v8.fyi%2FAuto-roll_-_deps%2F100271%2F%2B%2Frecipes%2Fsteps%2Froll_deps%2F0%2Fstdout V8 pins depot_tools to use it from auto-roller scripts. But: a) The bot doesn't seem to run the hooks. So the hook that disables the depot_tools auto-update is never run (if auto-update isn't disabled it will use ToT depot_tools always). b) Syncing is probably not recursive. So the bot will sync the depot_tools pinned in Chromium, but not the one pinned in V8. How does it even work? It seems to work somehow?!? Minor follow up problem: If there is ever a breakage in depot_tools like issue 843917 , V8 can't easily revert the pinned version in V8 for the auto-roller if the Chromium depot_tools are used...
,
May 26 2018
,
May 26 2018
After poking around, I've realized that we need a revision to be able to manually check out depot_tools, but can't find out at which reversion depot_tools is pinned in V8 without processing V8's DEPS. Instead, I've realized that we can add a new config replacing v8_tot, that configure Chromium solution not to checkout V8 at all and instead checkout it out as another solution, in which case it's DEPS will be processed. This of course still adds all unnecessary DEPS other than depot_tools, but we can selectively use this new config just for autoroller builders thereby avoiding checking out V8's DEPS anywhere else. WIP CL: https://crrev.com/c/1074491 (trial run: https://ci.chromium.org/swarming/task/3db405e73644f110, which did checkout V8's DEPS, but somehow placed entire V8 checkout into [START_DIR]/v8 instead of [START_DIR]/src/v8 as I expected).
,
May 26 2018
,
May 30 2018
Update: Posted http://shortn/_UplxozNaUH (sorry, internal only).
,
Jun 4 2018
We could also change the auto-roller and let it check out a stand-alone V8 and a workdir Chromium side-by-side. Not sure if that's glitch-free. We'd run the auto-roller script from the V8 checkout and its deport tools. We point it to the Chromium checkout for the rolling. It'd be cleaner than this V8-in-Chromium hack.
,
Jun 6 2018
Thank you! This is a great idea and is much simpler. CL: https://crrev.com/c/1089330
,
Jun 8 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build/+/b1e0be85ba8e02369440c7a934e9a5a570a16f62 commit b1e0be85ba8e02369440c7a934e9a5a570a16f62 Author: Sergiy Byelozyorov <sergiyb@chromium.org> Date: Fri Jun 08 08:11:41 2018 [V8] Use full V8 checkout for running release scripts R=machenbach@chromium.org Bug: 845425 Change-Id: If33b532abf66530a0a9334bd3f5e93fe828706a3 Reviewed-on: https://chromium-review.googlesource.com/1089330 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> [modify] https://crrev.com/b1e0be85ba8e02369440c7a934e9a5a570a16f62/scripts/slave/recipe_modules/v8/gclient_config.py [modify] https://crrev.com/b1e0be85ba8e02369440c7a934e9a5a570a16f62/scripts/slave/recipes/v8/auto_roll_deps.expected/stale_roll.json [modify] https://crrev.com/b1e0be85ba8e02369440c7a934e9a5a570a16f62/scripts/slave/recipes/v8/auto_roll_deps.py [modify] https://crrev.com/b1e0be85ba8e02369440c7a934e9a5a570a16f62/scripts/slave/recipes/v8/auto_roll_deps.expected/inconsistent_state.json [modify] https://crrev.com/b1e0be85ba8e02369440c7a934e9a5a570a16f62/scripts/slave/recipes/v8/auto_roll_deps.expected/stale_roll_experimental.json [modify] https://crrev.com/b1e0be85ba8e02369440c7a934e9a5a570a16f62/scripts/slave/recipes/v8/auto_roll_deps.expected/standard_experimental.json [modify] https://crrev.com/b1e0be85ba8e02369440c7a934e9a5a570a16f62/scripts/slave/recipes/v8/auto_roll_deps.expected/standard.json
,
Jul 5
This was fixed. Auto-roller is now using depot_tools DEPS-ed into V8. |
||||
►
Sign in to add a comment |
||||
Comment 1 by serg...@chromium.org
, May 26 2018