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

Issue 600481 link

Starred by 1 user
Status: Fixed
Owner:
ajuma@chromium.org
Closed: Apr 2016
Cc:
█ kbr@chromium.org
zmo@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 600556


Sign in to add a comment

gl_tests flakily failing to identify GPU on Mac 10.10 Debug (Intel)

Project Member Reported by ajuma@chromium.org, Apr 4 2016 
These tests have flaked twice today:

EXTMultisampleCompatibilityTest.DrawAlphaOneAndResolve
EXTMultisampleCompatibilityTest.DrawAndResolve
EXTMultisampleCompatibilityTest.TestSimple

They're crashing after the following error in the log:
[1718:1299:0404/120629:1363807512204:ERROR:gpu_test_config.cc(260)] Fail to identify GPU

Build log: https://build.chromium.org/p/chromium.gpu/builders/Mac%2010.10%20Debug%20%28Intel%29/builds/6020

Comment 1 by kbr@chromium.org, Apr 4 2016

Owner: ajuma@chromium.org
Status: Assigned (was: Untriaged)
zmo@ is taking a sick day today but he's the expert on gpu_test_config. Ali as pixel wrangler can you please build on Mac and try to reproduce this locally? Let me know if you need access to the actual hardware.

Comment 2 by ajuma@chromium.org, Apr 4 2016 

These failures are happening on a single physical bot:
https://chromium-swarm.appspot.com/restricted/bot/build212-m4

Most of the recent runs of gl_tests on that bot (some coming from the waterfall, some coming from mac_chromium_rel_ng) have failed.

I looked at recent runs on three other bots (build198-m4, build216-m4, build219-m4) and couldn't find a single failure.

Comment 3 by kbr@chromium.org, Apr 4 2016 

Very good diagnosis Ali. Could you please file a ticket with type "Build Infrastructure" about decommissioning this machine, and block this bug on that one? I assume that there is enough spare hardware in the swarming pool that one fewer machine won't matter. Thanks.

Comment 4 by ajuma@chromium.org, Apr 4 2016

Blockedon: 600556

Comment 5 by ajuma@chromium.org, Apr 8 2016

Status: Fixed (was: Assigned)
The bad bot was removed from the swarming pool in  issue 600556 .
►

Sign in to add a comment