Skip to content

DAOS-18495 object: use deep stack for IV involved ULT #17422

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
Open
NiuYawei wants to merge 1 commit into
base: master
Choose a base branch
from
Open

DAOS-18495 object: use deep stack for IV involved ULT #17422

NiuYawei wants to merge 1 commit into from

Conversation

@NiuYawei
Copy link
Contributor

@NiuYawei NiuYawei commented Jan 22, 2026

Use deep stack for IV involved ULTs.

Steps for the author:

  • Commit message follows the guidelines.
  • Appropriate Features or Test-tag pragmas were used.
  • Appropriate Functional Test Stages were run.
  • At least two positive code reviews including at least one code owner from each category referenced in the PR.
  • Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

  • Gatekeeper requested (daos-gatekeeper added as a reviewer).

@NiuYawei
DAOS-18495 object: use deep stack for IV involved ULT
06807e5 
Use deep stack for IV involved ULTs.

Signed-off-by: Niu Yawei <yawei.niu@hpe.com>
@NiuYawei NiuYawei requested review from a team as code owners January 22, 2026 04:34
@github-actions
Copy link

github-actions bot commented Jan 22, 2026

Ticket title is 'Random ranks are excluded with signal (6) with master branch.'
Status is 'Open'
Labels: 'test_2.8,testp1'
https://daosio.atlassian.net/browse/DAOS-18495

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

Reviewers

@liuxuezhao liuxuezhao liuxuezhao approved these changes

@Nasf-Fan Nasf-Fan Nasf-Fan approved these changes

Assignees

No one assigned

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@NiuYawei @liuxuezhao @Nasf-Fan