-
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: rsend_022_pos (32-bit only) #5654
Labels
Component: Test Suite
Indicates an issue with the test framework or a test case
Type: Architecture
Indicates an issue is specific to a single processor architecture
Comments
behlendorf
added
Type: Architecture
Indicates an issue is specific to a single processor architecture
Component: Test Suite
Indicates an issue with the test framework or a test case
labels
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 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component: Test Suite
Indicates an issue with the test framework or a test case
Type: Architecture
Indicates an issue is specific to a single processor architecture
System information
Describe the problem you're observing
The rsend_022_pos test case occasionally fails on 32-bit systems.
Describe how to reproduce the problem
The failure is reproducible by the buildbot.
Include any warning/errors/backtraces from the system logs
http://build.zfsonlinux.org/builders/Ubuntu%2014.04%20i686%20%28TEST%29/builds/675
The text was updated successfully, but these errors were encountered: