Skip to content

test: reduce the stress in the manyrma2 test #7379

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

hzhou
Copy link
Contributor

@hzhou hzhou commented Apr 11, 2025

Pull Request Description

The manyrma2 tests are often falsely triggered due to performance issue, especially for some configuration such as the asan tests. Lower the MAX_RUNS from 8 to 2 since our CI tests should focus on correctness. We'll focus on catching performance CI in the bench tests.

[skip warnings]

Author Checklist

  • Provide Description
    Particularly focus on why, not what. Reference background, issues, test failures, xfail entries, etc.
  • Commits Follow Good Practice
    Commits are self-contained and do not do two things at once.
    Commit message is of the form: module: short description
    Commit message explains what's in the commit.
  • Passes All Tests
    Whitespace checker. Warnings test. Additional tests via comments.
  • Contribution Agreement
    For non-Argonne authors, check contribution agreement.
    If necessary, request an explicit comment from your companies PR approval manager.

The manyrma2 tests are often falsely triggered due to performance issue.
Lower the MAX_RUNS from 8 to 2 since our CI tests should focus on
correctness. We'll focus on catching performance CI in the bench tests.
@hzhou
Copy link
Contributor Author

hzhou commented Apr 11, 2025

test:mpich/ch4/ofi

@hzhou hzhou requested a review from raffenet April 11, 2025 17:05
@raffenet
Copy link
Contributor

The performance tests are not stress tests, so they will not make up for the reduced stress in this test. I don't think this is the right change.

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.

2 participants