Skip to content

e4s oneapi ci: upgrade to use oneapi 2025.3#3807

Merged
alalazo merged 3 commits intospack:developfrom
eugeneswalker:e4s-ci-update-oneapi-stack
Mar 18, 2026
Merged

e4s oneapi ci: upgrade to use oneapi 2025.3#3807
alalazo merged 3 commits intospack:developfrom
eugeneswalker:e4s-ci-update-oneapi-stack

Conversation

@eugeneswalker
Copy link
Copy Markdown
Contributor

E4S OneAPI CI Stack: Upgrade to use use OneAPI 2025.3

@spackbot-triage spackbot-triage bot added the ci Issues related to Continuous Integration label Mar 12, 2026
@eugeneswalker eugeneswalker changed the title e4s oneapi ci: upgrade to use 2025.3 e4s oneapi ci: upgrade to use oneapi 2025.3 Mar 12, 2026
@eugeneswalker eugeneswalker force-pushed the e4s-ci-update-oneapi-stack branch from e164022 to 4029666 Compare March 12, 2026 20:33
@eugeneswalker
Copy link
Copy Markdown
Contributor Author

@spackbot run pipeline

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Mar 13, 2026

I've started that pipeline for you!

@eugeneswalker eugeneswalker requested a review from wspear March 13, 2026 16:59
@eugeneswalker
Copy link
Copy Markdown
Contributor Author

All CI is green!

Comment thread .ci/gitlab/.gitlab-ci.yml
@alalazo alalazo self-assigned this Mar 18, 2026
@alalazo alalazo merged commit 3b66f3c into spack:develop Mar 18, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Issues related to Continuous Integration e4s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants