Skip to content
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.

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

testsuite: gitlab ci cluster specific tests #6

Open
2 of 3 tasks
wihobbs opened this issue Oct 6, 2023 · 2 comments
Open
2 of 3 tasks

testsuite: gitlab ci cluster specific tests #6

wihobbs opened this issue Oct 6, 2023 · 2 comments

Comments

@wihobbs
Copy link
Member

wihobbs commented Oct 6, 2023

As @grondo and @garlick pointed out in flux-framework/flux-core#5482, there are some tests we'd like to run in our CI on real clusters in addition to the normal testsuite. Some ideas (opening this issue with the hope others will add to this list):

  • Checking that flux uri resolve slurm:jobid is able to properly resolve a Flux URI
  • Flux under Slurm works
  • Combinatorially testing MPI implementations on our clusters (this should probably be a whole issue by itself)
@chu11
Copy link
Member

chu11 commented Oct 6, 2023

although lower priority than the above, would we want to test with different python versions that are not the standard installed python? To make sure all the paths and what not are setup correctly? i.e. user uses python 3.X from /usr/tce and we make sure that works with the python 3.X from https://github.com/flux-framework/flux-python?? I think all Python we test in CI is the standard install python. (Edit: and perhaps this also double checks that all python dependencies are installed for each version? )

Note, I'm not sure the flux-python from above is installed yet ... so that maybe be another thing.

@wihobbs
Copy link
Member Author

wihobbs commented Oct 19, 2023

Snippet of @grondo and my weekly mtg:

  1. We're going to set up a new repository for flux-framework testing only. Iterating on core for integration tests might get cumbersome, and we want to test other framework projects.
  2. We'll run a nightly test of flux-core (do what was done in testsuite: run entire suite on LC hardware flux-core#5429) and some other stuff, too, that will be discussed in the Issues section of that new repo.
  3. There will be a Mattermost channel where the status of the nightly pipelines is reported.

@wihobbs wihobbs transferred this issue from flux-framework/flux-core Nov 21, 2023
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

No branches or pull requests

2 participants