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

Issue 704703 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Request for driver downgrade on build109-b1

Project Member Reported by ericrk@chromium.org, Mar 23 2017

Issue description

Per discussion in bug 704183, it would be good to downgrade the driver in build109-b1 to version 21.19.137.1, in order to confirm whether the unexpected failures are due to differences in driver version, or in swarming/non-swarming config.

Do we have archived drivers around anywhere (this was the 9/16/2016 driver, in the Crimson 16.9.2 installer). Otherwise I'm happy to dig it up.
 

Comment 1 by ericrk@chromium.org, Mar 23 2017

Cc: kbr@chromium.org jmad...@chromium.org

Comment 2 by pschm...@google.com, Mar 23 2017

Owner: pschmidt@chromium.org
Status: Assigned (was: Untriaged)
Status: Started (was: Assigned)
Done.  Effective starting with the next build which will be https://uberchromegw.corp.google.com/i/chromium.gpu.fyi/builders/Win7%20Release%20%28AMD%20R7%20240%29/builds/550

[build109-b1] out: AMD Radeon R7 200 Series                21.19.137.1

Comment 4 by kbr@chromium.org, Mar 24 2017

Peter: the slave looks like it's been offline since the card swap:
https://uberchromegw.corp.google.com/i/chromium.gpu.fyi/builders/Win7%20Release%20%28AMD%20R7%20240%29/

Could you check it out? Thanks.

Comment 5 by pschm...@google.com, Mar 24 2017

It just finished with https://uberchromegw.corp.google.com/i/chromium.gpu.fyi/builders/Win7%20Release%20%28AMD%20R7%20240%29/builds/549 and is (well was) rebooting.

For some reason the initial gclient sync is taking it's sweet time.  It will connect to the master shortly.

Comment 6 by kbr@chromium.org, Mar 24 2017

Ah, I see. I thought it might have been stuck offline for that ~4 hour gap. Sorry for the false alarm.

Comment 7 by b...@chromium.org, Mar 30 2018

Status: Fixed (was: Started)

Sign in to add a comment