Issue metadata
Sign in to add a comment
|
media.mse_cases failing on 7 builders |
||||||||||||||||||||||||
Issue descriptionmedia.mse_cases failing on 7 builders Builders failed on: - Android Nexus5 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf - Android Nexus5X Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20Perf - Android Nexus5X WebView Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf - Android Nexus6 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20Perf - Android Nexus6 WebView Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20WebView%20Perf - Android Nexus7v2 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf - Android One Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf All stories are failing. I'm going to disable the benchmark on android.
,
Oct 3 2017
,
Oct 3 2017
This isn't just mse_cases. watk@, could your 0dcff6d5a9baf3be4e5ef65e1ee552bd9ba0e6fc be causing these failures? Also, cc+= liberato@ since I have less familiarity with Android rendering-side stuff. I assume these failures are specific to Android (given the OP), so probably *not* general to MSE on any Chrome platform.
,
Oct 3 2017
https://chromium-swarm.appspot.com/task?id=38faefae94308f10 is a sample task. You can find the stack trace in there. That link will never expire. The whole stack trace is a bit long to copy paste in here, but I can put it in here if you want me to. I saw a bunch of failures on android bots in general. That's documented in bug 771397 . The CL you mention in #3 kinda fits in the commit position in that bug.
,
Oct 3 2017
re #3: I highly doubt it's related to my change: that code is mostly not compiled in a normal build. It would be trivial to see what's going on if the stack traces were symbolized though. Does anyone know how to do that?
,
Oct 4 2017
the bisect on 771397 has since found https://crrev.com/3b0c080b0bb28d3d8616d863f0302053dd1dbf42 as the cause. is there any reason to suspect that it isn't the same thing?
,
Oct 5 2017
Everything seems to be passing now; i spot checked with https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf/builds/436, and media.mse_cases is passing. So i think it was the same issue. I'll close this as a duplicate of the bug I mentioned. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by crouleau@chromium.org
, Oct 3 2017Components: Internals>Media>Session
Labels: OS-Android