chrome_public_test_apk failing on swarming staging consistently |
||
Issue descriptionhttps://ci.chromium.org/buildbot/chromium.swarm/Android%20N5%20Swarm/?limit=200 But it seems pretty stable on prod: https://ci.chromium.org/buildbot/chromium.android/KitKat%20Phone%20Tester%20%28rel%29/ This is worrying since staging should be nearly identical to prod at this point. I wonder what's up...? (Maybe related to bug 807370 ?)
,
Feb 9 2018
ooooohhhhhh... it's because '--recover-devices' isn't enabled for the chromium.swarm waterfall. The tests are actually failing the first 2 attempts on the main waterfall, but recovery makes it pass on the 3rd attempt. See all the black on https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=chrome_public_test_apk&tests=org.chromium.chrome.browser.TabsTest%23testToolbarSwipePrevTab I'll enable recovery on swarm and file a bug for the fery vlaky tests
,
Feb 9 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2369af2eca77738cd0b1dd7ed2ae05ea47bdd241 commit 2369af2eca77738cd0b1dd7ed2ae05ea47bdd241 Author: Benjamin Pastene <bpastene@chromium.org> Date: Fri Feb 09 22:47:05 2018 Enable device recovery & result details on chromium.swarm android bots. TBR=jbudorick@chromium.org Bug: 810610 Change-Id: I2cdafdec9eef1b646e51f3984243f38d345d2d92 Reviewed-on: https://chromium-review.googlesource.com/910651 Reviewed-by: Benjamin Pastene <bpastene@chromium.org> Reviewed-by: John Budorick <jbudorick@chromium.org> Commit-Queue: Benjamin Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#535862} [modify] https://crrev.com/2369af2eca77738cd0b1dd7ed2ae05ea47bdd241/testing/buildbot/chromium.swarm.json [modify] https://crrev.com/2369af2eca77738cd0b1dd7ed2ae05ea47bdd241/testing/buildbot/waterfalls.pyl
,
Feb 12 2018
much green: https://ci.chromium.org/buildbot/chromium.swarm/Android%20N5%20Swarm/ bug 810629 for test problems |
||
►
Sign in to add a comment |
||
Comment 1 by bpastene@chromium.org
, Feb 9 2018