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-16784 build: Tag 2.6.2 tb2 #15461

Merged
merged 1 commit into from
Nov 7, 2024
Merged

DAOS-16784 build: Tag 2.6.2 tb2 #15461

merged 1 commit into from
Nov 7, 2024

Conversation

phender
Copy link
Contributor

@phender phender commented Nov 6, 2024

Tag second test build for 2.6.2.

Skip-func-test: true
faults-enabled: false

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.

@phender
DAOS-16784 build: Tag 2.6.2 tb2
1947ad1 
Tag second test build for 2.6.2.

Skip-func-test: true
faults-enabled: false

Required-githooks: true

Signed-off-by: Phil Henderson <phillip.henderson@intel.com>
@phender phender requested a review from a team as a code owner November 6, 2024 23:45
@github-actions GitHub Actions
Copy link

github-actions bot commented Nov 6, 2024

Ticket title is 'Build 2.6.2 TB1'
Status is 'In Progress'
Labels: '2.6.1rc3_val,testp1'
https://daosio.atlassian.net/browse/DAOS-16784

@phender phender merged commit 3d65778 into release/2.6 Nov 7, 2024
46 of 48 checks passed
@phender phender deleted the pahender/DAOS-16784 branch November 7, 2024 01:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@daltonbohning daltonbohning daltonbohning approved these changes

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@phender @daltonbohning