Issue metadata
Sign in to add a comment
|
blink_perf.canvas stopped running on chromium-rel-win7-dual and android-galaxy-s5 |
||||||||||||||||||||||
Issue descriptionWe've had the blink_perf.canvas tests running with webgl_supported_shared_state since February, which disables the tests if the browser does not support webgl. On windows, this happened in the range 405221:405764 On android, it is in the range 405962:405972 Note we are still getting data from most windows/android bots, it's just the two in the bug title that are failing. Justin, any ideas how much of an issue this is, or what could have caused it?
,
Aug 5 2016
+kbr: i am also getting this same error for smoothness.tough_webgl_cases on chromium-rel-win7 bot only (other Windows bots are fine). Same revision range 405221:405764. Any ideas? https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%207%20Perf%20%282%29/builds/12744/steps/smoothness.tough_webgl_cases/logs/stdio
,
Aug 5 2016
This part of the log: (INFO) 2016-08-05 05:06:05,213 browser._LogBrowserInfo:113 OS: win win7 (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:120 GPU device 0: VENDOR = 0x102b, DEVICE = 0x532 (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:122 GPU Attributes: (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:124 adapter_luid : 0.0 (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:124 amd_switchable : False (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:124 basic_info_state : 1 (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:124 can_lose_context : False (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:124 context_info_state : 0 (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:124 direct_rendering : True (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:124 driver_date : 6-21-2006 (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:124 driver_vendor : Microsoft (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:124 driver_version : 6.1.7600.16385 (INFO) 2016-08-05 05:06:05,214 browser._LogBrowserInfo:124 dx_diagnostics_info_state: 0 indicates that only the on-board Matrox GPU is being recognized on this machine. Something's misconfigured on the machine.
,
Aug 9 2016
Thanks, Ken! I filed bug 635723 on how we can detect this more easily in the future, can you please weigh in there if you have any ideas? Vince, I'm assigning you this bug for triage. The GPU on build186-m1 is not being recognized, any ideas how to fix this?
,
Aug 9 2016
That would be because this machine doesn't have a GPU. It's in a non-GPU rack. Which GPU is needed?
,
Aug 9 2016
Thanks, dba! I'm sorry I had this mixed up with the bots that do have GPUs. Assigning back to Justin, the test owner--it seems like it's expected that there's no data? Ken, Justin, any idea if these tests may have gotten better at disabling themselves? They used to produce data on this machine, but the hardware has been the same for years.
,
Aug 9 2016
I can only speak for smoothness.tough_webgl_cases, but that test's only supposed to run on the bots on https://build.chromium.org/p/chromium.perf/builders/ which have GPUs -- for example, the multiple "Win 7 Nvidia GPU Perf" bots. I don't remember how the perf tests are assigned to bots and sharded among multiple bots. If that changed recently, that would explain why smoothness.tough_webgl_cases might have started spontaneously running on machines like https://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf%20%282%29 , which apparently don't have GPUs. I can't explain why the test might have previously been passing on this machine.
,
Aug 9 2016
,
Aug 9 2016
I think it's okay to close this as WontFix since we're not actually getting data from bots without GPUs. I'm still not quite sure how we ever got data, though. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sullivan@chromium.org
, Aug 5 2016