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

DAOS-16167 test: update soak test to use internal job scheduler (#14775) #15595

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

daltonbohning
Copy link
Contributor

Update soak to support using an internal job scheduler.

Skip-unit-tests: true
Skip-fault-injection-test: true
Test-tag: soak_smoke

Required-githooks: true

Before requesting gatekeeper:

  • Two review approvals and any prior change requests have been resolved.
  • Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
  • Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
  • Commit messages follows the guidelines outlined here.
  • Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

  • You are the appropriate gatekeeper to be landing the patch.
  • The PR has 2 reviews by people familiar with the code, including appropriate owners.
  • Githooks were used. If not, request that user install them and check copyright dates.
  • Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
  • All builds have passed. Check non-required builds for any new compiler warnings.
  • Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
  • If applicable, the PR has addressed any potential version compatibility issues.
  • Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
  • Extra checks if forced landing is requested
    • Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
    • No new NLT or valgrind warnings. Check the classic view.
    • Quick-build or Quick-functional is not used.
  • Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

Update soak to support using an internal job scheduler.

Skip-unit-tests: true
Skip-fault-injection-test: true
Test-tag: soak_smoke

Required-githooks: true

Signed-off-by: Maureen Jean <[email protected]>
@daltonbohning daltonbohning added the release-2.6.3 Targeted for 2.6.3 label Dec 11, 2024
@daltonbohning daltonbohning self-assigned this Dec 11, 2024
Copy link

Ticket title is 'Soak: update soak test to use internal job scheduler instead of depending on slurm'
Status is 'Awaiting backport'
Labels: 'daos_framework,request_for_2.6.3,soak'
https://daosio.atlassian.net/browse/DAOS-16167

@daltonbohning daltonbohning marked this pull request as ready for review December 11, 2024 20:17
@daltonbohning daltonbohning requested review from a team as code owners December 11, 2024 20:17
@daltonbohning daltonbohning added the clean-cherry-pick Cherry-pick from another branch that did not require additional edits label Dec 11, 2024
@daltonbohning daltonbohning added the forced-landing The PR has known failures or has intentionally reduced testing, but should still be landed. label Dec 11, 2024
@phender phender merged commit b1b52e3 into release/2.6 Dec 12, 2024
42 of 45 checks passed
@phender phender deleted the dbohning/daos-16167-2.6 branch December 12, 2024 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clean-cherry-pick Cherry-pick from another branch that did not require additional edits forced-landing The PR has known failures or has intentionally reduced testing, but should still be landed. release-2.6.3 Targeted for 2.6.3
Development

Successfully merging this pull request may close these issues.

3 participants