Skip to content

e4s cray rhel ci stack: re-enable and update for new cpe#47697

Merged
eugeneswalker merged 6 commits intospack:developfrom
eugeneswalker:e4s-cray-rhel-new-cpe
Jan 7, 2025
Merged

e4s cray rhel ci stack: re-enable and update for new cpe#47697
eugeneswalker merged 6 commits intospack:developfrom
eugeneswalker:e4s-cray-rhel-new-cpe

Conversation

@eugeneswalker
Copy link
Copy Markdown
Contributor

@eugeneswalker eugeneswalker commented Nov 20, 2024

This should resolve the cray-libsci issue with libdl we saw previously @haampie @kwryankrattiger

@spackbot-app spackbot-app bot added core PR affects Spack core functionality gitlab Issues related to gitlab integration labels Nov 20, 2024
@eugeneswalker eugeneswalker force-pushed the e4s-cray-rhel-new-cpe branch 3 times, most recently from 342c604 to a3ee007 Compare November 20, 2024 18:28
@eugeneswalker
Copy link
Copy Markdown
Contributor Author

@spackbot run pipeline

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Nov 20, 2024

I had a problem triggering the pipeline.

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

Pipeline isn't starting here. Gets hung up at "Pending — waiting for all-prechecks check to succeed"

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

eugeneswalker commented Nov 22, 2024

@spackbot run pipeline after manually installing missing boto3 packages on the Shell runners that Spack didn't bootstrap for me :)

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Nov 22, 2024

I've started that pipeline for you!

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

eugeneswalker commented Nov 23, 2024

The concretization here is whack. It is building some specs %[email protected] and some specs @[email protected] but it seems to not be respecting the packages:all:prefer:[%[email protected]] nor respecting the fact that the bundled compilers.yaml here has only two compilers registered [email protected] and [email protected] so not clear why/how the generate job and subsequent jobs are learning about these other compilers, let alone using them!

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

@spackbot run pipeline after fixing some issues locally on the runners

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Dec 9, 2024

I've started that pipeline for you!

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

@spackbot run pipeline

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Dec 11, 2024

I've started that pipeline for you!

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

@spackbot run pipeline

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Dec 17, 2024

I've started that pipeline for you!

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

@spackbot run pipeline after fixing fortran issue locally

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Dec 18, 2024

I've started that pipeline for you!

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

@spackbot run pipeline

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Dec 19, 2024

I've started that pipeline for you!

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

See succesfull e4s-cray-rhel pipeline results here:

The most recent pipeline run doesn't show this because both of the following are true

  1. e4s-cray-rhel is currently disabled via global GitLab project variable,
  2. 7ca25f5 restored SPACK_CI_DISABLE_STACKS in preparation for final merge of this PR

@eugeneswalker eugeneswalker merged commit 25ce6cc into spack:develop Jan 7, 2025
mtaillefumier pushed a commit to mtaillefumier/spack that referenced this pull request Jan 20, 2025
* e4s cray rhel ci stack: re-enable and update for new cpe, should fix cray libsci issue

* only run e4s-cray-rhel stack

* Mkae Autotools build_system point at correct build_directory

* remove selective enable of cray-rhel stacks

* restore SPACK_CI_DISABLE_STACKS

* use dot prefix to hide cray-sles jobs instead of comment-out

---------

Co-authored-by: Ryan Krattiger <[email protected]>
@haampie haampie added v0.23.1 PRs to backport for v0.23.1 and removed don't-merge-yet labels Feb 3, 2025
haampie pushed a commit that referenced this pull request Feb 3, 2025
* e4s cray rhel ci stack: re-enable and update for new cpe, should fix cray libsci issue

* only run e4s-cray-rhel stack

* Mkae Autotools build_system point at correct build_directory

* remove selective enable of cray-rhel stacks

* restore SPACK_CI_DISABLE_STACKS

* use dot prefix to hide cray-sles jobs instead of comment-out

---------

Co-authored-by: Ryan Krattiger <[email protected]>
teaguesterling pushed a commit to teaguesterling/spack that referenced this pull request Feb 5, 2025
* e4s cray rhel ci stack: re-enable and update for new cpe, should fix cray libsci issue

* only run e4s-cray-rhel stack

* Mkae Autotools build_system point at correct build_directory

* remove selective enable of cray-rhel stacks

* restore SPACK_CI_DISABLE_STACKS

* use dot prefix to hide cray-sles jobs instead of comment-out

---------

Co-authored-by: Ryan Krattiger <[email protected]>
mrmundt pushed a commit to mrmundt/spack that referenced this pull request Feb 17, 2025
* e4s cray rhel ci stack: re-enable and update for new cpe, should fix cray libsci issue

* only run e4s-cray-rhel stack

* Mkae Autotools build_system point at correct build_directory

* remove selective enable of cray-rhel stacks

* restore SPACK_CI_DISABLE_STACKS

* use dot prefix to hide cray-sles jobs instead of comment-out

---------

Co-authored-by: Ryan Krattiger <[email protected]>
@haampie haampie mentioned this pull request Feb 19, 2025
27 tasks
haampie pushed a commit that referenced this pull request Feb 19, 2025
* e4s cray rhel ci stack: re-enable and update for new cpe, should fix cray libsci issue

* only run e4s-cray-rhel stack

* Mkae Autotools build_system point at correct build_directory

* remove selective enable of cray-rhel stacks

* restore SPACK_CI_DISABLE_STACKS

* use dot prefix to hide cray-sles jobs instead of comment-out

---------

Co-authored-by: Ryan Krattiger <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build-systems core PR affects Spack core functionality cray e4s gitlab Issues related to gitlab integration v0.23.1 PRs to backport for v0.23.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants