chromite-to-chromium autoroller stuck |
|||
Issue descriptionhttps://chromite-chromium-roll.skia.org/ Hasn't rolled in a few days. Due to breakage on the amd64-generic tester on chrome's CQ: https://logs.chromium.org/v/?s=chromium%2Fbuildbucket%2Fcr-buildbucket.appspot.com%2F8943973165553696352%2F%2B%2Fsteps%2Fisolate_tests%2F0%2Fstdout """ isolate: isolate /b/swarming/w/ir/cache/builder/src/out_amd64-generic/Release/cacheinvalidation_unittests.isolate: partitioning deps: lstat /b/swarming/w/ir/cache/builder/src/build/cros_cache/chrome-sdk/tarballs/amd64-generic+10772.0.0+app-emulation: no such file or directory """ Some path probably changed, I'll take a look. (We should also try and make the blockages a little more visible. Maybe I can cc myself on all the rolls...)
,
Jun 12 2018
Actually, I can't make sense of this error. It looks like there were other failures that started the breakage, but the most recent breakage was probably triggered by: https://chromium-review.googlesource.com/c/chromiumos/chromite/+/1091272 How do I repo this particular failure locally? I think we'll need directions for gardeners as well.
,
Jun 12 2018
Yeah, I need to update some docs on this. It's trying to isolate the test and failing (ie: trying to upload the test and all its dependencies to our test artifact server) Here's how to (theoretically) repro what it's doing: - enter chrome-sdk w/ board amd64-generic - echo "cacheinvalidation_unittests" > swarm_targets - python tools/mb/mb.py gen --swarming-targets-file swarm_targets -b chromeos-amd64-generic-rel -m chromium.chromiumos out_amd64-generic/Release/ - autoninja -C out_amd64-generic/Release/ cacheinvalidation_unittests - ./tools/luci-go/linux64/isolate batcharchive -verbose -I isolateserver.appspot.com out_amd64-generic/Release/cacheinvalidation_unittests.isolated.gen.json And then it should fail like the bot.... But it isn't for me; it's succeeding. IDK why, I think something might be weirdly broken with the bot. I'll dig in deeper first thing tomorrow.
,
Jun 12 2018
Oh duhh, I was still running with an old chromite in #3. Updated to head and now it's failing like the bot. https://chromium-review.googlesource.com/c/chromium/src/+/1097503 for the fix
,
Jun 12 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/16c1b4fc216046662c8de63ab2be0ccfac816919 commit 16c1b4fc216046662c8de63ab2be0ccfac816919 Author: Ben Pastene <bpastene@chromium.org> Date: Tue Jun 12 22:16:35 2018 Roll chromite and fix qemu path in cros cache. Bug: 851753 Change-Id: I091358d649a991c66cf12ea059ba06c7998e185d Reviewed-on: https://chromium-review.googlesource.com/1097503 Reviewed-by: Achuith Bhandarkar <achuith@chromium.org> Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Achuith Bhandarkar <achuith@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#566602} [modify] https://crrev.com/16c1b4fc216046662c8de63ab2be0ccfac816919/DEPS [modify] https://crrev.com/16c1b4fc216046662c8de63ab2be0ccfac816919/build/config/chromeos/rules.gni
,
Jun 13 2018
Happily rolling again: https://chromite-chromium-roll.skia.org/ Filed https://bugs.chromium.org/p/skia/issues/detail?id=8067 to hopefully make the blockages more visible |
|||
►
Sign in to add a comment |
|||
Comment 1 by achuith@chromium.org
, Jun 12 2018Owner: achuith@chromium.org