Skip to content

Conversation

@bb-sycl
Copy link
Contributor

@bb-sycl bb-sycl commented Nov 22, 2022

Scheduled drivers uplift

@bb-sycl bb-sycl requested a review from a team as a code owner November 22, 2022 03:19
@MrSidims
Copy link
Contributor

Do we have plans to update windows drivers as well? It does look like the last time it was done is 2022-02-06
I see the following in git blame:

f4b31230fc861 (Alexander Batashev  2022-02-06 12:40:26 +0300  84)   "windows": {
f4b31230fc861 (Alexander Batashev  2022-02-06 12:40:26 +0300  85)     "compute_runtime": {
f4b31230fc861 (Alexander Batashev  2022-02-06 12:40:26 +0300  86)       "version": "101.1191",
f4b31230fc861 (Alexander Batashev  2022-02-06 12:40:26 +0300  87)       "url": "https://downloadmirror.intel.com/691496/igfx_win_101.1191.zip",
f4b31230fc861 (Alexander Batashev  2022-02-06 12:40:26 +0300  88)       "root": ""
f4b31230fc861 (Alexander Batashev  2022-02-06 12:40:26 +0300  89)     },

@MrSidims
Copy link
Contributor

MrSidims commented Nov 22, 2022

Tagging @bader @pvchupin old version of GPU driver prevents us from, for example, updating supported SPIR-V version to 1.4.

Or am I missing another testing config? I see also buildbot/dependency.conf file, but there situation is not much better:
18f873d (Yang,Yin 2022-03-15 19:25:48 +0800 35) gpu_driver_win=101.1404

@pvchupin
Copy link
Contributor

@MrSidims, in github actions we don't have an automatic mechanism to update driver on Windows. We don't have containers on windows.
In fact we don't have any testing on GPU on Windows as well in github actions.
So when you said that it prevents us from moving onto SPIRV-1.4, where exactly do you see the failure?

This specific GPU driver version is still broken. It doesn't have all dependencies needed for Ubuntu 20.

@pvchupin pvchupin closed this Nov 22, 2022
@pvchupin pvchupin deleted the ci/update_gpu_driver-linux-22.43.24558 branch November 22, 2022 17:35
@MrSidims
Copy link
Contributor

MrSidims commented Nov 22, 2022

@pvchupin Previously I attempted to update SPIR-V version in #6899 , and the regression was reported in #7018 in ESIMD testing on Windows.

In fact we don't have any testing on GPU on Windows as well in github actions.

Doesn't /verify command run the tests? Otherwise I don't see how these tests were run in Steffen's PR.

@MrSidims
Copy link
Contributor

MrSidims commented Nov 22, 2022

Doesn't /verify command run the tests?

It does look like it doesn't, at least right now. Guess it's a chance for me to squeeze a patch :)

@pvchupin
Copy link
Contributor

@MrSidims I think you are confusing jenkins and github actions. These are 2 different systems.
Let's chat offline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants