New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 635185 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ w...@chromium.org
crouleau@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

android tough video cases ___127.0.0.1_ tests running sometimes and then alerting

Project Member Reported by crouleau@chromium.org, Aug 5 2016 
Tests that have not received data in some time:

Last rev	Test	Stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_crowd1080.ogv_canvas_true_browser	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_crowd1080.ogv_canvas_true_gpu	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_crowd1080_vp9.webm_browser	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_crowd1080_vp9.webm_canvas_true_browser	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_crowd1080_vp9.webm_canvas_true_gpu	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_crowd1080_vp9.webm_gpu	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_crowd720_vp9.webm_browser	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_crowd720_vp9.webm_gpu	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_smpte_3840x2160_60fps_vp9.webm_browser	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_smpte_3840x2160_60fps_vp9.webm_gpu	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.m4a_type_audio_browser	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.m4a_type_audio_gpu	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.mp3_type_audio_browser	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.mp3_type_audio_gpu	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.mp4_browser	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.mp4_canvas_true_browser	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.mp4_canvas_true_gpu	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.mp4_gpu	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.ogg_type_audio_browser	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.ogg_type_audio_gpu	stdio
409480	ChromiumPerf/android-nexus5/media.android.tough_video_cases/cpu_utilization/http___127.0.0.1_52632_video.html?src_tulip2.ogv_browser	stdio


There is only one data point for these graphs, and they are duplicate of existing graphs that don't have "___127.0.0.1_" in them. 

Since the Chromium AV Perf Sheriff alerting config has the pattern 

"ChromiumPerf/*/media.android.tough_video_cases/*/*" in it, the tests are picked up for monitoring when they first run and then since they only run once they alert two days later that the data stopped. 

Last time this happened we deleted the data with the "___127.0.0.1_" in it and the "List monitored tests" button on the Chromium AV Perf Sheriff alerting config stopped showing those tests. But now we have another data point. 

Attached is the output from the test:
Log File contents.html
1.3 MB View Download

Comment 1 by w...@chromium.org, Aug 5 2016 

Still not sure why sometimes we get the http___127.. prefix and usually don't.

I think we can avoid the issue entirely though, by cleaning up the names for our metrics. i.e., instead of "video.html?src=tulip2.ogv" we should just call it "tulip2.ogv". I'll investigate doing that.

Comment 2 by benhenry@chromium.org, Mar 10 2017

Components: Speed>Benchmarks>Waterfall
Labels: -Performance-Waterfall
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 12 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment