Issue metadata
Sign in to add a comment
|
No data received for media.tough_video_cases from linux-release since 463837 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 17 2017
Потеря зg соединения 2sim на устройстве
,
Apr 24 2017
Bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981762985992661392 indicated http://crrev/463872 as the likely cause of this. capn: It appears that after your commit http://crrev/463872, the perf lab is no longer getting results from GPU processes while running the media benchmarks on Linux. Apparently the Chrome GPU processes are no longer started during these benchmarks. Could you please confirm if this is expected? Thanks.
,
Apr 24 2017
Issue 713863 has been merged into this issue.
,
Apr 24 2017
Issue 713865 has been merged into this issue.
,
Apr 25 2017
My CL causes us to use SwiftShader for WebGL support on the CPU, when the GPU is blacklisted. It makes the GPU inaccessible for anything else, and the GPU process is only started when running WebGL content. So iff these perf lab systems are using outdated hardware, then this is expected.
,
Apr 25 2017
Simon: We have stopped receiving media benchmark measurements from GPU processes on linux-release bots, and this indicates that the lab might be using a GPU that is outdated and blacklisted. Is there any way for you to check the hardware in the lab to confirm if it is the case? I'm still getting GPU process measurements when I run the benchmarks on my local machine, so this does appear to be a machine-specific issue. Thanks.
,
Apr 25 2017
+nednguyen for hardware setup question I took a quick peek at the output from the swarming task on the waterfall and it appears to be using SwiftShader as capn@ mentioned (https://chromium-swarm.appspot.com/task?id=35bdcf0452469e10&refresh=10&show_raw=1). Not sure where to get the machine specs (the swarming page lists the gpu as a Matrox G200eR2), but Ned might know.
,
Apr 25 2017
The Matrox G200 is an ancient GPU, which nowadays is used as an embedded GPU on many server motherboards (hence the eR2 suffix - embedded Revision 2). It's definitely a blacklisted GPU, so the fallback to SwiftShader is expected.
,
Oct 30 2017
,
Jan 8 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by johnchen@chromium.org
, Apr 17 2017