Revert OneAPI 2025.3 pinning in coverage workflow#2998
Open
antonwolfy wants to merge 1 commit into
Open
Conversation
Reverts #2887 which pinned Intel OneAPI to 2025.3 in the generate_coverage workflow due to a known 2026.0 DPC++ compiler issue (CMPLRLLVM-75178) causing a segfault during sycl-post-link. With OneAPI 2026.1 released, the pinning is no longer needed, so this restores installing the latest Intel OneAPI packages and installing dpctl from the pinned requirements file. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
View rendered docs @ https://intelpython.github.io/dpnp/pull/2998/index.html |
Contributor
|
Array API standard conformance tests for dpnp=0.21.0dev3=py313h509198e_2 ran successfully. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This reverts the changes from #2887, which pinned Intel OneAPI to 2025.3 in the
generate_coverageworkflow.#2887 introduced the pinning to work around a known 2026.0 DPC++ compiler issue (CMPLRLLVM-75178) causing a segfault during
sycl-post-link. With OneAPI 2026.1 now released, the pinning is no longer needed.