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-16572 rebuild: some refine and log #15208

Draft
wants to merge 2 commits into
base: release/2.6
Choose a base branch
from

Conversation

liuxuezhao
Copy link
Contributor

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.

Copy link

github-actions bot commented Sep 27, 2024

Ticket title is 'After pool extend noticing rebuild timeouts on soak online testing with 2.6.1-rc1 image.'
Status is 'Awaiting backport'
Labels: '2.6.1_issue,manual_test,soak'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-16572

@liuxuezhao liuxuezhao force-pushed the lxz/agg_rb_debug_26 branch 4 times, most recently from dbcad7c to abee2f7 Compare October 11, 2024 04:33
@github-actions github-actions bot added the priority Ticket has high priority (automatically managed) label Oct 21, 2024
@liuxuezhao liuxuezhao changed the title DAOS-16572 rebuild: add some log DAOS-16572 rebuild: some refine and log Oct 21, 2024
@liuxuezhao liuxuezhao force-pushed the lxz/agg_rb_debug_26 branch 2 times, most recently from 3717f78 to 79971b7 Compare October 28, 2024 10:56
Signed-off-by: Xuezhao Liu <xuezhao.liu@intel.com>
Skip-nlt: true

Signed-off-by: Xuezhao Liu <xuezhao.liu@intel.com>
@daosbuild1
Copy link
Collaborator

Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-15208/10/display/redirect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority Ticket has high priority (automatically managed)
Development

Successfully merging this pull request may close these issues.

2 participants