Skip to content

DAOS-18927 test: remove dfs tag from dfuse build tests (#18160)#18231

Draft
daltonbohning wants to merge 1 commit into
release/2.8from
dbohning/daos-18927-2.8
Draft

DAOS-18927 test: remove dfs tag from dfuse build tests (#18160)#18231
daltonbohning wants to merge 1 commit into
release/2.8from
dbohning/daos-18927-2.8

Conversation

@daltonbohning
Copy link
Copy Markdown
Contributor

@daltonbohning daltonbohning commented May 12, 2026

Remove the dfs tag from long-running dfuse build tests since it is overkill to run them. Tag just the pr build test with dfuse.

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).

@daltonbohning
DAOS-18927 test: remove dfs tag from dfuse build tests (#18160)
4a01415 
Remove the dfs tag from long-running dfuse build tests since it is
overkill to run them. Tag just the pr build test with dfuse.

Signed-off-by: Dalton Bohning <dalton.bohning@hpe.com>
@daltonbohning daltonbohning self-assigned this May 12, 2026
@daltonbohning daltonbohning added clean-cherry-pick Cherry-pick from another branch that did not require additional edits forced-landing The PR has known failures or has intentionally reduced testing, but should still be landed. approved-to-merge PR has received release branch merge approval labels May 12, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 12, 2026

Ticket title is 'ftest: remove dfs tag from long-running dfuse build tests'
Status is 'Awaiting backport'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-18927

@github-actions github-actions Bot added the priority Ticket has high priority (automatically managed) label May 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@daltonbohning daltonbohning

Labels

approved-to-merge PR has received release branch merge approval clean-cherry-pick Cherry-pick from another branch that did not require additional edits forced-landing The PR has known failures or has intentionally reduced testing, but should still be landed. priority Ticket has high priority (automatically managed)

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@daltonbohning