Skip to content

Conversation

@daltonbohning
Copy link
Contributor

Reduce expected threshold from 300% to 250%.
Discard performance of first read with caching enabled. Also misc test cleanup.

Test-tag: test_dfuse_caching_check
Test-repeat: 10
Skip-unit-tests: true
Skip-fault-injection-test: true

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 daltonbohning self-assigned this Feb 10, 2026
@daltonbohning daltonbohning added the clean-cherry-pick Cherry-pick from another branch that did not require additional edits label Feb 10, 2026
@github-actions
Copy link

Ticket title is 'dfuse/caching_check.py:DfuseCachingCheck.test_dfuse_caching_check - Expected a speedup of 3 but got 2.8059'
Status is 'Awaiting backport'
Labels: 'ci_master_weekly,weekly_test'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-16983

@github-actions github-actions bot added the priority Ticket has high priority (automatically managed) label Feb 10, 2026
@daosbuild3
Copy link
Collaborator

Test stage Functional Hardware Medium completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17538/1/testReport/

Reduce expected threshold from 300% to 250%.
Discard performance of first read with caching enabled.
Also misc test cleanup.

Test-tag: test_dfuse_caching_check
Test-repeat: 10
Skip-unit-tests: true
Skip-fault-injection-test: true

Signed-off-by: Dalton Bohning <dalton.bohning@hpe.com>
@daltonbohning daltonbohning added unclean-cherry-pick Indicates that a cherry-pick had merge conflicts that needed resolving. and removed clean-cherry-pick Cherry-pick from another branch that did not require additional edits labels Feb 10, 2026
@daltonbohning daltonbohning force-pushed the dbohning/daos-16983-2.6 branch from 02d59f6 to d9ad3a8 Compare February 10, 2026 19:08
@daltonbohning daltonbohning marked this pull request as ready for review February 10, 2026 21:28
@daltonbohning daltonbohning requested review from a team as code owners February 10, 2026 21:28
@daltonbohning daltonbohning requested a review from a team February 10, 2026 22:38
@daltonbohning daltonbohning added the forced-landing The PR has known failures or has intentionally reduced testing, but should still be landed. label Feb 10, 2026
@daltonbohning daltonbohning merged commit 2726bd3 into release/2.6 Feb 10, 2026
41 of 42 checks passed
@daltonbohning daltonbohning deleted the dbohning/daos-16983-2.6 branch February 10, 2026 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

forced-landing The PR has known failures or has intentionally reduced testing, but should still be landed. priority Ticket has high priority (automatically managed) unclean-cherry-pick Indicates that a cherry-pick had merge conflicts that needed resolving.

Development

Successfully merging this pull request may close these issues.

3 participants