Skip to content

Conversation

@bb-sycl
Copy link
Contributor

@bb-sycl bb-sycl commented Oct 4, 2022

Scheduled drivers uplift

@bb-sycl bb-sycl requested a review from a team as a code owner October 4, 2022 03:31
@pvchupin
Copy link
Contributor

pvchupin commented Oct 4, 2022

@smaslov-intel, @againull , it seems all tests fail in Level Zero mode with the new driver uplift. Could you please help to triage?

@smaslov-intel
Copy link
Contributor

@smaslov-intel, @againull , it seems all tests fail in Level Zero mode with the new driver uplift. Could you please help to triage?

Lots of failures are like this. I am going to try reproduce locally.
Is the new driver installed anywhere?

$ "env" "SYCL_DEVICE_FILTER=ext_oneapi_level_zero:gpu" "/__w/llvm/llvm/build/SYCL/Assert/Output/assert_in_kernels.cpp.tmp.out"
# redirected output from '/__w/llvm/llvm/build/SYCL/Assert/Output/assert_in_kernels.cpp.tmp.txt':
terminate called after throwing an instance of 'sycl::_V1::runtime_error'
  what():  Native API failed. Native API returns: -997 (The plugin has emitted a backend specific error) -997 (The plugin has emitted a backend specific error)

note: command had no output on stdout or stderr
error: command failed with exit status: -6

@pvchupin
Copy link
Contributor

pvchupin commented Oct 4, 2022

Lots of failures are like this. I am going to try reproduce locally. Is the new driver installed anywhere?

I don't think so. This PR is first attempt to try that.
We probably should be building container with that at least, not doing that today.
That's this one: https://github.com/intel/compute-runtime/releases/tag/22.39.24347

@bader
Copy link
Contributor

bader commented Oct 5, 2022

We probably should be building container with that at least, not doing that today.

We were doing this before @pvchupin removed it in #6581. :)
See this comment.

@pvchupin
Copy link
Contributor

pvchupin commented Oct 5, 2022

We were doing this before @pvchupin removed it in #6581. :) See [this comment]

We did it wrong imo. Instead of producing a PR for unstable version uplift simultaneously with stable version uplift, the task which builds unstable containers should just always pickup the latest driver and build the container. No additional PR needed.
I'll submit a new PR if there is a need for such container.

@pvchupin
Copy link
Contributor

Closing this PR. Weekly uplift will retrigger this again automatically. Driver is still broken.

@pvchupin pvchupin closed this Oct 13, 2022
@pvchupin pvchupin deleted the ci/update_gpu_driver-linux-22.39.24347 branch October 13, 2022 19:59
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