Skip to content

Conversation

@sarnex
Copy link
Contributor

@sarnex sarnex commented Apr 1, 2025

Seems broken

@sarnex sarnex requested a review from a team as a code owner April 1, 2025 14:46
@sarnex sarnex merged commit 03f26a6 into intel:sycl Apr 1, 2025
14 checks passed
@sarnex sarnex temporarily deployed to WindowsCILock April 1, 2025 14:47 — with GitHub Actions Inactive
@sarnex sarnex temporarily deployed to WindowsCILock April 1, 2025 15:21 — with GitHub Actions Inactive
@sarnex sarnex temporarily deployed to WindowsCILock April 1, 2025 15:21 — with GitHub Actions Inactive
@sarnex
Copy link
Contributor Author

sarnex commented Apr 1, 2025

@intel/unified-runtime-reviewers Any ideas why we still can't use the latest L0? We get no device again, see here (ignore this commit was before the driver update commit, its using the new driver because of some docker stuff)

@kbenzie
Copy link
Contributor

kbenzie commented Apr 1, 2025

@intel/unified-runtime-reviewers Any ideas why we still can't use the latest L0? We get no device again, see here (ignore this commit was before the driver update commit, its using the new driver because of some docker stuff)

@nrspruit any insights?

@kbenzie
Copy link
Contributor

kbenzie commented Apr 1, 2025

Had a chat with @pbalcer about this, there is a direct dependency between the compute runtime version and the level zero version, the compute runtime has a manifest stating the version it expects https://github.com/intel/compute-runtime/blob/25.09.32961.7/manifests/manifest.yml#L50-L56 which I'm guessing needs to align @sarnex

@sarnex
Copy link
Contributor Author

sarnex commented Apr 1, 2025

Thanks, let me try that

sarnex added a commit that referenced this pull request Apr 2, 2025
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.

2 participants