Skip to content

check_prop_source: improve output clarity #11517

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

Conversation

wca
Copy link
Contributor

@wca wca commented Jan 25, 2021

Motivation and Context

When tests using check_prop_source fail, it's helpful to see the original data that shows why it failed.

Description

Log a note explaining what was expected and what was observed, when checking property value and source.

How Has This Been Tested?

ZTS

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)

Checklist:

wca added 2 commits January 24, 2021 18:16
There is an identical definition in zfs_set_common.kshlib already.

Signed-off-by:	Will Andrews <will@firepipe.net>
Instead of just failing, indicate the expected and actual value and source
as a NOTE.  Tests using this failed in an earlier version of the changeset
and this information helped find the cause.

Signed-off-by:	Will Andrews <will@firepipe.net>
@wca wca mentioned this pull request Jan 25, 2021
12 tasks
@behlendorf behlendorf added the Status: Accepted Ready to integrate (reviewed, tested) label Jan 25, 2021
jsai20 pushed a commit to jsai20/zfs that referenced this pull request Mar 30, 2021
Instead of just failing, indicate the expected and actual value and
source as a NOTE.  Tests using this failed in an earlier version of
the changeset and this information helped find the cause.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by:	Will Andrews <will@firepipe.net>
Closes openzfs#11517
sempervictus pushed a commit to sempervictus/zfs that referenced this pull request May 31, 2021
Instead of just failing, indicate the expected and actual value and
source as a NOTE.  Tests using this failed in an earlier version of
the changeset and this information helped find the cause.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by:	Will Andrews <will@firepipe.net>
Closes openzfs#11517
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.

2 participants