Closed Bug 974684 Opened 7 years ago Closed 7 years ago
Upgrade Windows 8 Nvidia drivers to 335
This is required for bug 938395.
Before asking IT, I will do it once manually and see where we're at.
Assignee: nobody → armenzg
To test on staging first. I assume this is the package to install: http://www.nvidia.com/download/driverResults.aspx/73314/en-uk
Summary: upgrade windows 8 nvidia drivers to 334.89 → Upgrade Windows 8 Nvidia drivers to 334.89
What does it have higher priority? This bug or bug 971926? Adding Benoit.
I'd say this bug. This bug is blocking known brokenness. Where as bug 971926 is about trying to prevent new brokenness from being introduced.
Nvidia has released GeForce 335.23 WHQL drivers, can this driver be installed instead? http://www.nvidia.com/download/driverResults.aspx/73780/en-us
(In reply to NVD from comment #5) > Nvidia has released GeForce 335.23 WHQL drivers, can this driver be > installed instead? > > http://www.nvidia.com/download/driverResults.aspx/73780/en-us It could be. Is there a particular reason to?
Summary: Upgrade Windows 8 Nvidia drivers to 334.89 → Upgrade Windows 8 Nvidia drivers to 335.23
Only one job has failed. I'm re-triggering it. Jeff, is there any specific log that you would like to inspect to verify that things are working as expected? I'm happy to deploy as-is since it does not seem to affect any jobs (except the one I'm waiting on).
(In reply to Armen Zambrano [:armenzg] (Release Engineering) (EDT/UTC-4) from comment #8) > Only one job has failed. I'm re-triggering it. > > Jeff, is there any specific log that you would like to inspect to verify > that things are working as expected? > > I'm happy to deploy as-is since it does not seem to affect any jobs (except > the one I'm waiting on). No, there's nothing I'm looking for.
The re-trigger passed.
Is there an ETA for this being deployed?
Monday as per dep bug.
Last night this was deployed and backed out. Investigating.
Stragglers in bug 1004813.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
For posterity, what ended up happening here? The latest comments suggest that we tried to upgrade and backed it out...yet this bug is RESOLVED FIXED.
All the comments ended up on the dependent bug. We found there was an issue on the deployment that would make the first jobs to burn right away. On the second time and half we got it right.
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.