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

MPI tests within the integration module tests should be run separately from the rest #3570

Closed
HideakiImamura opened this issue May 18, 2022 · 0 comments · Fixed by #3606
Closed
Labels
CI Continuous integration. contribution-welcome Issue that welcomes contribution. no-stale Exempt from stale bot

Comments

@HideakiImamura
Copy link
Member

What is an issue?

Currently, the MPI tests within the integration module tests often fail due to lack of resources. e.g. https://github.com/optuna/optuna/runs/6473604671?check_suite_focus=true. The tests itself will pass without problems if rerun, but it is too costly to rerun the entire integration module tests from scratch to rerun just the MPI tests.

I suggest separating MPI testing from the rest of the tests to reduce the cost of CI reruns.

@HideakiImamura HideakiImamura added CI Continuous integration. contribution-welcome Issue that welcomes contribution. labels May 18, 2022
@g-votte g-votte added the no-stale Exempt from stale bot label May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous integration. contribution-welcome Issue that welcomes contribution. no-stale Exempt from stale bot
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants