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-16639 object: fix assertion #15218

Closed
wants to merge 4 commits into from
Closed

DAOS-16639 object: fix assertion #15218

wants to merge 4 commits into from

Conversation

wangdi1
Copy link
Contributor

@wangdi1 wangdi1 commented Sep 29, 2024

Invalid hole extent might be left by process_hole_ult(), so let's skip it.

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.

Invalid hole extent might be left by process_hole_ult(),
so let's skip it.

Signed-off-by: Di Wang <ddiwang@google.com>
@wangdi1 wangdi1 requested review from a team as code owners September 29, 2024 05:28
@wangdi1 wangdi1 requested a review from liuxuezhao September 29, 2024 05:28
Copy link

github-actions bot commented Sep 29, 2024

Ticket title is 'agg_diff_preprocess() Assertion '!extent->ae_hole' failed'
Status is 'Open'
Labels: 'scrubbed_2.8'
https://daosio.atlassian.net/browse/DAOS-16639

@wangdi1 wangdi1 requested a review from jolivier23 September 29, 2024 05:28
liuxuezhao
liuxuezhao previously approved these changes Sep 30, 2024
johannlombardi
johannlombardi previously approved these changes Oct 1, 2024
jolivier23
jolivier23 previously approved these changes Oct 4, 2024
@wangdi1
Copy link
Contributor Author

wangdi1 commented Oct 16, 2024

close this one for fixing the branch name, and moved to #15329

@wangdi1 wangdi1 closed this Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants