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

Issue 673356 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 709247
Owner:
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

performance browser test failures on chromium.perf Win 7 Nvidia GPU Perf

Project Member Reported by eyaich@chromium.org, Dec 12 2016

Issue description

We have been seeing several failures of performance browser tests on this bot in the last 200 builds: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%207%20Nvidia%20GPU%20Perf?numbuilds=200

 

Most recent failure is here: 

https://chromium-swarm.appspot.com/task?id=330a9b5b47a93310&refresh=10&show_raw=1

As you can see from the logs there are some udp errors which may be unrelated to these tests, but wondered if you had any thoughts given the log stream?
 
Owner: pkotw...@chromium.org
I'm afraid I have zero knowledge of performance_browser_tests and am not the right person to ask.

+pkotwicz: Would you be able to triage this one?

Comment 2 by eyaich@chromium.org, Dec 15 2016

ping

It is pretty consistently failing every few builds.  

Latest build where it fails: 
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%207%20Nvidia%20GPU%20Perf/builds/86

https://chromium-swarm.appspot.com/task?id=331a260633e74410&refresh=10&show_raw=1

is the latest run with the log output.  I am happy to help debug, but could use some guidance.  Was hoping someone more familiar with the test might be able to look at the log output.  

Hmm; it just passed in a recent test. Log here: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FWin_7_ATI_GPU_Perf%2F122%2F%2B%2Frecipes%2Fsteps%2Fperformance_browser_tests_on_ATI_GPU_on_Windows_on_Windows-2008ServerR2-SP1%2F0%2Fstdout

So looks like a flake? There are some errors in there which look like red herrings.

Comment 5 by eyaich@chromium.org, Dec 22 2016

Given that it fails 50% of the time, I think it is worth investigation.  

It would be great if someone familiar with the test could take a look at the log and see if they see anything that jumps out.  

Otherwise maybe we disable for windows?
This is still failing regularly (146/200 runs). Any update on it? Also, its not a telemetry test, how would I go about disabling this test on this bot?
Sorry, that I missed this. However, I am not the right owner for this. I am unfamiliar with perf tests and work on Android not Windows
Cc: picksi@chromium.org
CCing picksi@ who might know of someone in Windows land who understands perf tests
Owner: m...@chromium.org
sending to miu, another owner of perfomance_browser_tests. It looks like the tests all have [SUCCESS] status, but the exit code is 1.

Lots of this in the logs:
[2628:1204:0330/045154.613:INFO:CONSOLE(43)] "Uncaught TypeError: capture_stream.stop is not a function", source: chrome-extension://ddchlicdkolnonkihahngkmmmjnjlkkf/performance.js (43)

Full recent log: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FWin_7_Nvidia_GPU_Perf%2F549%2F%2B%2Frecipes%2Fsteps%2Fperformance_browser_tests_on_NVIDIA_GPU_on_Windows_on_Windows-2008ServerR2-SP1%2F0%2Fstdout

Comment 10 by m...@chromium.org, Apr 16 2017

Mergedinto: 709247
Status: Duplicate (was: Assigned)

Sign in to add a comment