-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Test case: zfs_rename_006_pos #5647
Labels
Component: Test Suite
Indicates an issue with the test framework or a test case
Comments
behlendorf
added
the
Component: Test Suite
Indicates an issue with the test framework or a test case
label
Jan 24, 2017
behlendorf
added a commit
to behlendorf/zfs
that referenced
this issue
Jan 24, 2017
Associate disabled test cases with existing open issues, update update comments to be consistent and disable a few test cases. The goal is for all enabled test to pass reliably. The following test cases have been disabled due to infrequent failures during automated testing. Several of these test cases were previous disabled only for the kmemleak builder but have subsequently been observed on other automated builders. - zfs_destroy_001_pos - openzfs#5635 - zfs_rename_006_pos - openzfs#5647 - zfs_rename_009_neg - openzfs#5648 - zpool_clear_001_pos - openzfs#5634 - zfs_allow_010_pos - openzfs#5646 - reservation_018_pos - openzfs#5642 - snapused_004_pos - openzfs#5513 Signed-off-by: Brian Behlendorf <[email protected]>
behlendorf
added a commit
to behlendorf/zfs
that referenced
this issue
Jan 24, 2017
Associate disabled test cases with existing open issues, update comments to be consistent and disable a few additional test cases. The goal is for all enabled test to pass reliably. The following test cases have been disabled due to infrequent failures during automated testing. Several of these test cases were previous disabled only for the kmemleak builder but have subsequently been observed on other automated builders. - zfs_destroy_001_pos - openzfs#5635 - zfs_rename_006_pos - openzfs#5647 - zfs_rename_009_neg - openzfs#5648 - zpool_clear_001_pos - openzfs#5634 - zfs_allow_010_pos - openzfs#5646 - reservation_018_pos - openzfs#5642 - snapused_004_pos - openzfs#5513 - rsend_022_pos - openzfs#5654 Signed-off-by: Brian Behlendorf <[email protected]>
behlendorf
added a commit
to behlendorf/zfs
that referenced
this issue
Jan 25, 2017
Associate disabled test cases with existing open issues, update comments to be consistent, disable a few additional test cases. The goal is for all enabled test to pass 100% reliably. The following test cases have been disabled due to infrequent failures during automated testing. Several of these test cases were previous disabled only for the kmemleak builder but have subsequently been observed on other automated builders. - zfs_destroy_001_pos - openzfs#5635 - zfs_rename_006_pos - openzfs#5647 - zfs_rename_009_neg - openzfs#5648 - zpool_clear_001_pos - openzfs#5634 - zfs_allow_010_pos - openzfs#5646 - reservation_018_pos - openzfs#5642 - snapused_004_pos - openzfs#5513 - rsend_022_pos - openzfs#5654 - history_006_neg - openzfs#5657 - history_008_pos - openzfs#5658 Signed-off-by: Brian Behlendorf <[email protected]>
behlendorf
added a commit
to behlendorf/zfs
that referenced
this issue
Jan 25, 2017
Associate disabled test cases with existing open issues, update comments to be consistent, disable a few additional test cases. The goal is for all enabled test to pass 100% reliably. The following test cases have been disabled due to infrequent failures during automated testing. Several of these test cases were previous disabled only for the kmemleak builder but have subsequently been observed on other automated builders. - zfs_destroy_001_pos - openzfs#5635 - zfs_rename_006_pos - openzfs#5647 - zfs_rename_009_neg - openzfs#5648 - zpool_clear_001_pos - openzfs#5634 - zfs_allow_010_pos - openzfs#5646 - reservation_018_pos - openzfs#5642 - snapused_004_pos - openzfs#5513 - rsend_022_pos - openzfs#5654 - rsend_024_pos - openzfs#5665 - history_008_pos - openzfs#5658 - history_006_neg - openzfs#5657 - history_008_pos - openzfs#5658 Signed-off-by: Brian Behlendorf <[email protected]>
behlendorf
added a commit
to behlendorf/zfs
that referenced
this issue
Jan 26, 2017
Associate disabled test cases with existing open issues, update comments to be consistent, disable a few additional test cases. The goal is for all enabled test to pass 100% reliably. The following test cases have been disabled due to infrequent failures during automated testing. Several of these test cases were previous disabled only for the kmemleak builder but have subsequently been observed on other automated builders. - zfs_destroy_001_pos - openzfs#5635 - zfs_rename_006_pos - openzfs#5647 - zfs_rename_009_neg - openzfs#5648 - zpool_clear_001_pos - openzfs#5634 - zfs_allow_010_pos - openzfs#5646 - reservation_018_pos - openzfs#5642 - snapused_004_pos - openzfs#5513 - rsend_022_pos - openzfs#5654 - rsend_024_pos - openzfs#5665 - history_008_pos - openzfs#5658 - history_006_neg - openzfs#5657 - history_008_pos - openzfs#5658 - zfs_inherit_003_pos - openzfs#5669 Signed-off-by: Brian Behlendorf <[email protected]>
behlendorf
added a commit
that referenced
this issue
Jan 26, 2017
Associate disabled test cases with existing open issues, update comments to be consistent, disable a few additional test cases. The goal is for all enabled test to pass 100% reliably. The following test cases have been disabled due to infrequent failures during automated testing. Several of these test cases were previous disabled only for the kmemleak builder but have subsequently been observed on other automated builders. - zfs_destroy_001_pos - #5635 - zfs_rename_006_pos - #5647 - zfs_rename_009_neg - #5648 - zpool_clear_001_pos - #5634 - zfs_allow_010_pos - #5646 - reservation_018_pos - #5642 - snapused_004_pos - #5513 - rsend_022_pos - #5654 - rsend_024_pos - #5665 - history_008_pos - #5658 - history_006_neg - #5657 - history_008_pos - #5658 - zfs_inherit_003_pos - #5669 Reviewed-by: Giuseppe Di Natale <[email protected]> Reviewed-by: George Melikov <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Closes #5649
wli5
pushed a commit
to wli5/zfs
that referenced
this issue
Feb 28, 2017
Associate disabled test cases with existing open issues, update comments to be consistent, disable a few additional test cases. The goal is for all enabled test to pass 100% reliably. The following test cases have been disabled due to infrequent failures during automated testing. Several of these test cases were previous disabled only for the kmemleak builder but have subsequently been observed on other automated builders. - zfs_destroy_001_pos - openzfs#5635 - zfs_rename_006_pos - openzfs#5647 - zfs_rename_009_neg - openzfs#5648 - zpool_clear_001_pos - openzfs#5634 - zfs_allow_010_pos - openzfs#5646 - reservation_018_pos - openzfs#5642 - snapused_004_pos - openzfs#5513 - rsend_022_pos - openzfs#5654 - rsend_024_pos - openzfs#5665 - history_008_pos - openzfs#5658 - history_006_neg - openzfs#5657 - history_008_pos - openzfs#5658 - zfs_inherit_003_pos - openzfs#5669 Reviewed-by: Giuseppe Di Natale <[email protected]> Reviewed-by: George Melikov <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Closes openzfs#5649
wli5
pushed a commit
to wli5/zfs
that referenced
this issue
Feb 28, 2017
Associate disabled test cases with existing open issues, update comments to be consistent, disable a few additional test cases. The goal is for all enabled test to pass 100% reliably. The following test cases have been disabled due to infrequent failures during automated testing. Several of these test cases were previous disabled only for the kmemleak builder but have subsequently been observed on other automated builders. - zfs_destroy_001_pos - openzfs#5635 - zfs_rename_006_pos - openzfs#5647 - zfs_rename_009_neg - openzfs#5648 - zpool_clear_001_pos - openzfs#5634 - zfs_allow_010_pos - openzfs#5646 - reservation_018_pos - openzfs#5642 - snapused_004_pos - openzfs#5513 - rsend_022_pos - openzfs#5654 - rsend_024_pos - openzfs#5665 - history_008_pos - openzfs#5658 - history_006_neg - openzfs#5657 - history_008_pos - openzfs#5658 - zfs_inherit_003_pos - openzfs#5669 Reviewed-by: Giuseppe Di Natale <[email protected]> Reviewed-by: George Melikov <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Closes openzfs#5649
GregorKopka
pushed a commit
to GregorKopka/zfs
that referenced
this issue
Jan 7, 2019
zfs_rename_006_pos has been flaky in the past because it was missing a call to block_device_wait to ensure the zvols it creates are present before running dd. Whenever this this happened, zfs_rename_009_neg would also fail because the first test would leak a zvol clone that it did not know how to clean up. This patch fixes the root cause and reenables the test. It also fixes some minor grammar errors. Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Tom Caputi <[email protected]> Closes openzfs#5647 Closes openzfs#5648 Closes openzfs#8088
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
Describe the problem you're observing
Rarely observed failure of zfs_rename_006_pos during automated testing.
Describe how to reproduce the problem
Reproducible by the buildbot.
Include any warning/errors/backtraces from the system logs
http://build.zfsonlinux.org/builders/Amazon%202015.09%20x86_64%20Release%20%28TEST%29/builds/1057/steps/shell_11/logs/log
The text was updated successfully, but these errors were encountered: