Skip to content

Run framework and pipeline tests on IRIS sequentially rather than in parallel - #627

Merged
yousefmoazzam merged 2 commits into
mainfrom
framework-pipeline-tests-iris-sequential
Sep 11, 2025
Merged

yousefmoazzam merged 2 commits into
mainfrom
framework-pipeline-tests-iris-sequential

Conversation

@yousefmoazzam

@yousefmoazzam yousefmoazzam commented Sep 8, 2025 •

Copy link
Copy Markdown
Collaborator

Debugging if running the framework and small data pipeline tests sequentially rather than in parallel avoids the cupy-import issues that are frequently seen.

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have made corresponding changes to the documentation

@yousefmoazzam
yousefmoazzam force-pushed the framework-pipeline-tests-iris-sequential branch from 48f9a9a to f285a3b Compare September 11, 2025 11:44
@yousefmoazzam
yousefmoazzam force-pushed the framework-pipeline-tests-iris-sequential branch from f285a3b to 3adc34f Compare September 11, 2025 11:51
@yousefmoazzam

Copy link
Copy Markdown
Collaborator Author

Running the workflows sequentially rather than in parallel does indeed seem to show consistent behaviour in the jobs not getting the cupy-import error, or the "unhealthy" pod error.

So, I think this is worth merging, to then be able to potentially have a more reliable experience with the IRIS GPU runners.

@yousefmoazzam
yousefmoazzam merged commit 21db6da into main Sep 11, 2025
5 checks passed
@yousefmoazzam
yousefmoazzam deleted the framework-pipeline-tests-iris-sequential branch September 11, 2025 12:21
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