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.

Sign up for GitHub

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

Jump to bottom

DAOS-16500 build: Move to Leap 15.6 (#15561) #15656

Open
wants to merge 1 commit into
base: release/2.6
Choose a base branch
from
Open

DAOS-16500 build: Move to Leap 15.6 (#15561) #15656

wants to merge 1 commit into from
+30 −11

Conversation

phender
Copy link
Contributor

@phender phender commented Dec 21, 2024

Test with Leap 15.6 instead of Leap 15.5.

Skip-unit-tests: true
Skip-func-hw-test: true
Skip-func-test-leap15: false
Skip-func-test-el8: true
Skip-fault-injection-test: 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.

@phender
DAOS-16500 build: Move to Leap 15.6 (#15561)
76d9269 
Test with Leap 15.6 instead of Leap 15.5.

Skip-unit-tests: true
Skip-func-hw-test: true
Skip-func-test-leap15: false
Skip-func-test-el8: true
Skip-fault-injection-test: true

Signed-off-by: Phil Henderson <phillip.henderson@hpe.com>
@phender phender requested a review from a team as a code owner December 21, 2024 04:35
@github-actions GitHub Actions
Copy link

Ticket title is 'DAOS 2.6.2 SLES 15 SP6 support'
Status is 'In Review'
Labels: 'lrz,request_for_2.6.3,testp1'
https://daosio.atlassian.net/browse/DAOS-16500

@phender phender added the unclean-cherry-pick Indicates that a cherry-pick had merge conflicts that needed resolving. label Dec 21, 2024
@phender
Copy link
Contributor Author

phender commented Dec 21, 2024

Only the changes to the utils/rpms/daos.spec required manual intervention in the cherry-pick due to differences in version/release and changelog.

@daosbuild1
Copy link
Collaborator

Test stage Functional on Leap 15.6 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15656/1/execution/node/821/log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ryon-jensen ryon-jensen ryon-jensen approved these changes

@daltonbohning daltonbohning Awaiting requested review from daltonbohning

Assignees
No one assigned
Labels
unclean-cherry-pick Indicates that a cherry-pick had merge conflicts that needed resolving.
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@phender @daosbuild1 @ryon-jensen