Skip to content

Implement a temporary workaround to avoid usage of 2025.0 components in GutHub actions #2131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 4 commits into from
Oct 28, 2024
Merged

Implement a temporary workaround to avoid usage of 2025.0 components in GutHub actions #2131

merged 4 commits into from
Oct 28, 2024

Conversation

antonwolfy
Copy link
Contributor

@antonwolfy antonwolfy commented Oct 27, 2024 •
edited
Loading

The PR is about to unblock GitHub actions until all components from 2025.0 release will be published (currently it's done only for part of components which breaks the workflows).

  • Have you provided a meaningful PR description?
  • Have you added a test, reproducer or referred to 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?
  • If this PR is a work in progress, are you filing the PR as a draft?

@antonwolfy antonwolfy self-assigned this Oct 27, 2024
@antonwolfy antonwolfy force-pushed the temporary-limit-to-use-2025.0-release-in-public-ci branch from ef315f9 to 1f04d8e Compare October 27, 2024 19:15
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Oct 27, 2024 •
edited
Loading

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

@antonwolfy antonwolfy changed the title Implement a temporary workaround to avoid usage of 2025.0 components in GutHUb actions Implement a temporary workaround to avoid usage of 2025.0 components in GutHub actions Oct 27, 2024
@antonwolfy antonwolfy marked this pull request as ready for review October 28, 2024 11:30
vlad-perevezentsev
vlad-perevezentsev approved these changes Oct 28, 2024
View reviewed changes
Copy link
Collaborator

@vlad-perevezentsev vlad-perevezentsev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!
Thank you @antonwolfy for timely implementation of this w/a

@antonwolfy antonwolfy merged commit 1857d78 into master Oct 28, 2024
46 checks passed
@antonwolfy antonwolfy deleted the temporary-limit-to-use-2025.0-release-in-public-ci branch October 28, 2024 14:19
github-actions bot added a commit that referenced this pull request Oct 28, 2024
@github-actions
Implement a temporary workaround to avoid usage of 2025.0 component…
5e0ae45 
…s in GutHub actions (#2131)

* Pin DPC++ and OneMKL to stable 2024.2 version in meta.yaml

* Limit DPC++, OneMKL and TBB versions for building docs and coverage run

* Limit max compiler and MMKL versions for build

* Step dpctl required version 1857d78
@antonwolfy antonwolfy mentioned this pull request Oct 30, 2024
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@vlad-perevezentsev vlad-perevezentsev vlad-perevezentsev approved these changes

@npolina4 npolina4 Awaiting requested review from npolina4

@vtavana vtavana Awaiting requested review from vtavana vtavana is a code owner

Assignees

@antonwolfy antonwolfy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@antonwolfy @vlad-perevezentsev