Issue metadata
Sign in to add a comment
|
maps_pixel_test on Android failing on chromium.gpu/Android Release (Nexus 5X) |
||||||||||||||||||||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of tmartino@chromium.org maps_pixel_test on Android failing on chromium.gpu/Android Release (Nexus 5X) Builders failed on: - Android Release (Nexus 5X): https://build.chromium.org/p/chromium.gpu/builders/Android%20Release%20%28Nexus%205X%29 We've got two assertion failures so far today on this test. They're few and far between so it's not having a big impact on the build, but probably still worth investigating.
,
Feb 5 2018
From this failing build: https://ci.chromium.org/buildbot/chromium.gpu/Android%20Release%20%28Nexus%205X%29/1994 https://chromium-swarm.appspot.com/task?id=3b7fc4b746091e10&refresh=10&show_raw=1 We can see the generated image: http://chromium-browser-gpu-tests.commondatastorage.googleapis.com/view_test_results.html?e082a634cab32b5dbbb20a44c28c4007d4bc805d_Android_Release_Nexus_5X__telemetry I'm not sure what's gone wrong because the successful runs don't upload their images. Yuly, any chance you could do a spot check and see what's wrong with these runs? Do we need to mark the test flaky? Because our harness interacts with the Maps team's test, we should be able to understand exactly what's on screen at the end of the test. Thanks.
,
Feb 5 2018
The image in #2 comes from a device in landscape orientation and not in portrait. Portrait image contains slightly bigger portion of the map. Catapult should be configuring the device to be in portrait, not sure why it would fail.
,
Feb 5 2018
We do: https://chrome-internal.googlesource.com/infradata/config/+/master/configs/chromium-swarm/scripts/android.py#245 I don't see any errors in the bot's logs when that gets set. Could just be weird device flake.
,
Feb 5 2018
FWIW, same device (build384-m1--device7) passed maps_pixel_test here: https://chromium-swarm.appspot.com/task?id=3b39cdca950ea110&refresh=10&show_raw=1 Maybe a race between changing orientation and running test? I've observed it can take a while for Android to apply orientation change.
,
Feb 16 2018
Another failure https://ci.chromium.org/buildbot/tryserver.chromium.android/android_optional_gpu_tests_rel/18698 Looks like the same root cause as issue 807370
,
Feb 16 2018
That device's user_rotation had a value=1. I'm fixing that in https://chrome-internal-review.googlesource.com/c/infradata/config/+/570958. Seems to be a dupe of bug 807370 ? |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tmartino@chromium.org
, Feb 5 2018Owner: kbr@chromium.org
Status: Assigned (was: Available)