-
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: history_008_pos #5658
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 25, 2017
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 <behlendorf1@llnl.gov>
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 <behlendorf1@llnl.gov>
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 <behlendorf1@llnl.gov>
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 <dinatale2@llnl.gov> Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 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 <dinatale2@llnl.gov> Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 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 <dinatale2@llnl.gov> Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#5649
|
behlendorf
pushed a commit
that referenced
this issue
Sep 25, 2017
* Add 'zfs bookmark' coverage (zfs_bookmark_cliargs) * Add OpenZFS 8166 coverage (zpool_scrub_offline_device) * Fix "busy" zfs_mount_remount failures * Fix bootfs_003_pos, bootfs_004_neg, zdb_005_pos local cleanup * Update usage of $KEEP variable, add get_all_pools() function * Enable history_008_pos and rsend_019_pos (non-32bit builders) * Enable zfs_copies_005_neg, update local cleanup * Fix zfs_send_007_pos (large_dnode + OpenZFS 8199) * Fix rollback_003_pos (use dataset name, not mountpoint, to unmount) * Update default_raidz_setup() to work properly with more than 3 disks * Use $TEST_BASE_DIR instead of hardcoded (/var)/tmp for file VDEVs * Update usage of /dev/random to /dev/urandom Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: loli10K <ezomori.nozomu@gmail.com> Issue #6086 Closes #5658 Closes #6143 Closes #6421 Closes #6627 Closes #6632
FransUrbo
pushed a commit
to FransUrbo/zfs
that referenced
this issue
Apr 28, 2019
* Add 'zfs bookmark' coverage (zfs_bookmark_cliargs) * Add OpenZFS 8166 coverage (zpool_scrub_offline_device) * Fix "busy" zfs_mount_remount failures * Fix bootfs_003_pos, bootfs_004_neg, zdb_005_pos local cleanup * Update usage of $KEEP variable, add get_all_pools() function * Enable history_008_pos and rsend_019_pos (non-32bit builders) * Enable zfs_copies_005_neg, update local cleanup * Fix zfs_send_007_pos (large_dnode + OpenZFS 8199) * Fix rollback_003_pos (use dataset name, not mountpoint, to unmount) * Update default_raidz_setup() to work properly with more than 3 disks * Use $TEST_BASE_DIR instead of hardcoded (/var)/tmp for file VDEVs * Update usage of /dev/random to /dev/urandom Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: loli10K <ezomori.nozomu@gmail.com> Issue openzfs#6086 Closes openzfs#5658 Closes openzfs#6143 Closes openzfs#6421 Closes openzfs#6627 Closes openzfs#6632
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 history_008_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/CentOS%206.7%20x86_64%20%28TEST%29/builds/4260
The text was updated successfully, but these errors were encountered: