Skip to content

Revert OneAPI 2025.3 pinning in coverage workflow#2998

Open
antonwolfy wants to merge 1 commit into
masterfrom
revert-gh-2887
Open

Revert OneAPI 2025.3 pinning in coverage workflow#2998
antonwolfy wants to merge 1 commit into
masterfrom
revert-gh-2887

Conversation

@antonwolfy

@antonwolfy antonwolfy commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

This reverts the changes from #2887, which pinned Intel OneAPI to 2025.3 in the generate_coverage workflow.

#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.

  • Have you provided a meaningful PR description?
  • Have you added a test, reproducer or referred to an issue with a reproducer?
  • Have you tested your changes locally for CPU and GPU devices?
  • Have you made sure that new changes do not introduce compiler warnings?
  • Have you checked performance impact of proposed changes?
  • Have you added documentation for your changes, if necessary?
  • Have you added your changes to the changelog?

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>
@github-actions

Copy link
Copy Markdown
Contributor

View rendered docs @ https://intelpython.github.io/dpnp/pull/2998/index.html

@github-actions

Copy link
Copy Markdown
Contributor

Array API standard conformance tests for dpnp=0.21.0dev3=py313h509198e_2 ran successfully.
Passed: 1373
Failed: 2
Skipped: 5

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.

1 participant