Issue metadata
Sign in to add a comment
|
No data received for webrtc_perf_tests from webrtc-android-tests-nexus4-jellybean since 15605 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 7 2017
ivoc@: Do you know the reason for these data stoppage alerts?
,
Apr 18 2017
This seems to be caused by my CL that was intended to improve the reliability of these tests: https://codereview.webrtc.org/2568883004 , but I don't understand why that would cause data stoppage on these Nexus devices. kjellander: Do you know why this happened? Could it be that my change increased the run time of the test too much for these devices?
,
Apr 19 2017
When I look at https://chromeperf.appspot.com/group_report?bug_id=709356 now it only shows webrtc-android-tests-nexus4-jellybean and those devices were removed since they were unreliable and JB wasn't supporting some adb feature that now is required in Chrome infra. So the data stoppage for that one is expected. I assume the other reported stoppages have recovered and because of that is no longer referencing this bug.
,
Apr 19 2017
Hmm, I had another look and the data stoppage is still there for other devices (that are still around) like webrtc-android-tests-nexus6-lollipop. Unfortunately the old logs are no longer there ( bug 712551 ) but a newer run https://build.chromium.org/p/client.webrtc.perf/builders/Android32%20Tests%20%28L%20Nexus6%29/builds/2505/steps/webrtc_perf_tests/logs/stdio only lists this entry matching EchoDetectorAndDefaultDesktopApm: I 1239.253s run_tests_on_device(ZX1G22LLPD) RESULT echo_detector_call_durations_total: EchoDetectorAndDefaultDesktopApm= {120025.700000, 1583.092091} us Is that an expected outcome of your CL? I don't think a longer runtime as mentioned in #3 should affect this. In the CL it seems you're actually removing these loggings at https://codereview.webrtc.org/2568883004/diff/40001/webrtc/modules/audio_processing/residual_echo_detector_complexity_unittest.cc so I guess this data stoppage is a just a result of that?
,
Apr 20 2017
Oh, you're right, I guess I did remove that part of the logging, so then this is completely expected. I guess what confused me is that these alerts were all from Android bots, so I assumed it would be something specific to those devices. Anyway, thanks for looking into this! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by peah@chromium.org
, Apr 7 2017