A lot of media_unittests failing on Jelly Bean Tester |
|||||
Issue descriptionThe media_unittests seem to have started failing in build #6020: https://uberchromegw.corp.google.com/i/chromium.android/builders/Jelly%20Bean%20Tester/builds/6020 Link to flakiness dashboard for media_unittests on Jelly Bean Tester: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=media_unittests&builder=chromium.android%3AJelly%20Bean%20Tester I don't really know what could cause this.. having a look at logcat dumps.
,
Sep 9 2016
Seems unlikely as I don't see a test that would try to use a GPU program. I don't see a suspicious commit, reverting mine, just to be safe.
,
Sep 12 2016
Revert didn't help, so I'll reland the commit. https://uberchromegw.corp.google.com/i/chromium.android/builders/Jelly%20Bean%20Tester/builds/6034/steps/media_unittests/logs/stdio has a timeout causing all tests to fail.
,
Sep 12 2016
Actually the revert didn't go through, let me retry to land it.
,
Sep 12 2016
Actually, this bot is fail lots of tests from different test suites, unless a lot of jelly-bean-ruining changes landed recently this might be a problem with the device. Yoland, can we look at the device / reboot it?
,
Sep 12 2016
added +bpastene, master of infra status #1: it actually started at build #6007 #5: the devices reboot every time at `provision device` stage, but since build 6014 (https://uberchromegw.corp.google.com/i/chromium.android/builders/Jelly%20Bean%20Tester/builds/6013), devices start to gradually go missing. I just ssh in and there is only one device attached. Not sure whether that's related to the device failing. I will check on what happened to the devices and maybe run a couple of local run
,
Sep 12 2016
,
Sep 12 2016
I ran the tests locally, they fail more than they do on bots.
,
Sep 13 2016
(revert didn't help, unreverting) |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by gsennton@chromium.org
, Sep 9 2016