Issue metadata
Sign in to add a comment
|
Frequent data stoppage alert for media.mse_cases on Android |
||||||||||||||||||||||
Issue descriptionThis data stoppage alert fires routinely, and so far has been resolved by ignoring it every time.
,
May 20 2016
,
May 23 2016
Why are you ignoring the alerts? For example, just looking at the first one, no data has come in since May 19: https://chromeperf.appspot.com/report?sid=90ad2e41a095db573fae09ec4631a8f78aa6859ff12788606e85447d50e96037 Would you prefer to disable this test?
,
May 24 2016
Adding Dan back.
,
May 24 2016
Dan can speak to this as well. We currently have a rotation of people to look into the alerts. I think that we have been having trouble understanding exactly what to do to triage the alerts, and so people are simply ignoring them. It's a problem that we are hoping to fix.
,
May 24 2016
I wrote a doc on triaging these, it's a bit verbose, but maybe it's a starting point? https://docs.google.com/document/d/1cF2Ny3UYbXq2y3fZaygUSz_3lVc0SOrSRZwXqGjjKgo/edit
,
May 24 2016
Looks like the test has recovered, but I don't know why it was failing. For example, this is a failure. runtest.py saw an exit code of 87 from something and "adb devices" looks to be the last thing that ran. I guess we can see if this happens again and try to debug the cause. /usr/bin/python /b/build/slave/Android_Galaxy_S5_Perf__3_/build/src/build/android/test_runner.py perf --print-step media.mse_cases --verbose --blacklist-file /b/build/slave/Android_Galaxy_S5_Perf__3_/build/src/out/bad_devices.json --output-chartjson-data=/tmp/tmpZIz3St I 0.004s Main command: /b/build/slave/Android_Galaxy_S5_Perf__3_/build/src/build/android/test_runner.py perf --print-step media.mse_cases --verbose --blacklist-file /b/build/slave/Android_Galaxy_S5_Perf__3_/build/src/out/bad_devices.json --output-chartjson-data=/tmp/tmpZIz3St I 0.004s TimeoutThread-1-for-MainThread [host]> /b/build/slave/Android_Galaxy_S5_Perf__3_/build/src/third_party/android_tools/sdk/platform-tools/adb devices E 0.012s Main File not found /b/build/slave/Android_Galaxy_S5_Perf__3_/build/src/out/step_results/media.mse_cases <Thread(Thread-1, started 140718020540160)> ProcessRead: proc.stdout finished. <Thread(Thread-1, started 140718020540160)> ProcessRead: cleaning up. <Thread(Thread-2, started daemon 140718012147456)> TimedFlush: Finished <Thread(Thread-1, started 140718020540160)> ProcessRead: finished. exit code (as seen by runtest.py): 87 @@@STEP_FAILURE@@@
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 1 2016
,
Jul 9 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 15 2016
Annie, any update on this bug?
,
Jul 15 2016
Assignign back to reporter to debug with the doc linked in #6 and info in #7 if it happens again.
,
Jul 22 2016
Pinging Dan. Could you comment on #12?
,
Jul 25 2016
Since the data is currently flowing there is not too much I can do. I'll leave this open until the next time it fails.
,
Aug 5 2016
Leaving this open as per #14.
,
Aug 9 2016
,
Oct 18 2016
Dan, is this something we should still be working on?
,
Oct 18 2016
+Frank.
,
Oct 18 2016
+ Thomas
,
Dec 5 2016
,
Dec 19 2016
,
Mar 8 2018
Stale. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sande...@chromium.org
, May 20 2016