webview_licenses failing flakily on linux_android_rel_ng, blocking CQ jobs |
|||
Issue descriptionhttps://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng?numbuilds=200 Many builds are failing the webview_licenses step, and some succeed while others fail. https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/100756 is one example of such a build. All the affected files seem to be under build/linux/debian_jessie_arm64-sysroot/ . This is affecting CQ jobs and apparently causing retries which is leading to linux_android_rel_ng timing out getting build URLs (see https://codereview.chromium.org/2116593004 ).
,
Jul 8 2016
... because it didn't modify checklicenses: https://codesearch.chromium.org/chromium/src/tools/checklicenses/checklicenses.py?rcl=0&l=650
,
Jul 8 2016
I wonder why this isn't showing up on the main waterfall bot https://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/28746 ...?
,
Jul 8 2016
Don't know. Revert just landed, though.
,
Jul 8 2016
#3: theory: this failed on gce hosts that previously ran an N5X (i.e., arm64) build since LARNG shares a trigger GCE pool with android_n5x_swarming_rel?
,
Jul 8 2016
Ah, that could very well be the case. Those two bots definitely shouldn't be sharing slave-dirs. It's pretty much a clobber each time they switch builds.
,
Jul 8 2016
Hmm, good point, I hadn't thought of that.
,
Jul 8 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build.git/+/f79668abb95a1d762e1d3da6bb04113d7ecec5b7 commit f79668abb95a1d762e1d3da6bb04113d7ecec5b7 Author: bpastene <bpastene@chromium.org> Date: Fri Jul 08 23:07:22 2016 Split arm and arm64 android trybots work directories. Also delete android_swarming_rel trybot. BUG= 626784 Review-Url: https://codereview.chromium.org/2137733002 [modify] https://crrev.com/f79668abb95a1d762e1d3da6bb04113d7ecec5b7/masters/master.tryserver.chromium.android/builders.pyl [modify] https://crrev.com/f79668abb95a1d762e1d3da6bb04113d7ecec5b7/scripts/slave/recipe_modules/chromium_tests/trybots.py [delete] https://crrev.com/cf5cdaa14775c27153ec44868e2a33513789198f/scripts/slave/recipes/chromium_trybot.expected/full_tryserver_chromium_android_android_swarming_rel.json
,
Jul 8 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/tools/build_limited/scripts/slave/+/a7018f6952c46c69d74741cf73420658c14e3a1a commit a7018f6952c46c69d74741cf73420658c14e3a1a Author: recipe-roller <recipe-roller@chromium.org> Date: Fri Jul 08 23:18:22 2016
,
Jul 8 2016
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra.git/+/740d62aef55b787b739cdd4668c9ed1da8b15f0b commit 740d62aef55b787b739cdd4668c9ed1da8b15f0b Author: recipe-roller <recipe-roller@chromium.org> Date: Fri Jul 08 23:28:37 2016 Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (e.g. depot_tools) into downstream projects (e.g. tools/build). More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug (or complain) build: https://crrev.com/f79668abb95a1d762e1d3da6bb04113d7ecec5b7 Split arm and arm64 android trybots work directories. (bpastene@chromium.org) R=bpastene@chromium.org BUG= 626784 TBR=martiniss@chromium.org,phajdan.jr@chromium.org Review-Url: https://codereview.chromium.org/2133863004 [modify] https://crrev.com/740d62aef55b787b739cdd4668c9ed1da8b15f0b/infra/config/recipes.cfg
,
Jul 11 2016
This is still happening frequently. https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng?numbuilds=200
,
Jul 11 2016
I guess I shouldn't be surprised given that /build/linux/debian_*-sysroot/ shows up in .gitignore. We may need to clobber some hosts.
,
Jul 11 2016
(host checkouts, that is, not just output directories)
,
Jul 11 2016
Yeah, since these are gce, we can do a mass respawn that will wipe all local checkouts. The problem is doing this with as little disruption as possible. I think I might just do it all in one go later tonight. Since these failures aren't actively blocking anything, I think it can wait that long. Feel free to tell me otherwise if you disagree.
,
Jul 11 2016
That sounds OK.
,
Jul 12 2016
I respawned them all yesterday evening. We should be good. |
|||
►
Sign in to add a comment |
|||
Comment 1 by jbudorick@chromium.org
, Jul 8 2016