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

update max_variance limit in zdb_block_size_histogram test for CI #15252

Merged
merged 1 commit into from
Sep 9, 2023

Conversation

ednadolski-ix
Copy link
Contributor

Commit 2d78434 had previously updated this hardcoded limit to allow for CI testing. As there is no deterministic pass/fail value, the need has arisen for one more small increase.

Motivation and Context

Required to avoid spurious failures in CI test runs.

Description

Update the hardcoded max_variances limit in the test script. Further allowance is needed, since this test does not have a conclusive/deterministic pass/fail criteria.

How Has This Been Tested?

Tested on local system and in CI pipeline.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
  • Documentation (a change to man pages or other documentation)

Spurious test failures lead to unnecessary investigative/diagnostic efforts and are preferrably avoided.

Checklist:

Commit 2d78434 had previously
updated this hardcoded limit to allow for CI testing. As there
is no deterministic pass/fail value, the need has arisen for
one more small increase.

Signed-off-by: Edmund Nadolski <[email protected]>
@behlendorf behlendorf added the Status: Accepted Ready to integrate (reviewed, tested) label Sep 8, 2023
@behlendorf behlendorf merged commit 0ee9b02 into openzfs:master Sep 9, 2023
behlendorf pushed a commit to behlendorf/zfs that referenced this pull request Sep 19, 2023
Commit 2d78434 had previously
updated this hardcoded limit to allow for CI testing. As there
is no deterministic pass/fail value, the need has arisen for
one more small increase.

Reviewed-by: Alexander Motin <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Edmund Nadolski <[email protected]>
Closes openzfs#15252
behlendorf pushed a commit that referenced this pull request Sep 19, 2023
Commit 2d78434 had previously
updated this hardcoded limit to allow for CI testing. As there
is no deterministic pass/fail value, the need has arisen for
one more small increase.

Reviewed-by: Alexander Motin <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Edmund Nadolski <[email protected]>
Closes #15252
lundman pushed a commit to openzfsonwindows/openzfs that referenced this pull request Dec 12, 2023
Commit 2d78434 had previously
updated this hardcoded limit to allow for CI testing. As there
is no deterministic pass/fail value, the need has arisen for
one more small increase.

Reviewed-by: Alexander Motin <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Edmund Nadolski <[email protected]>
Closes openzfs#15252
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Accepted Ready to integrate (reviewed, tested)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants