-
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_destroy_010_pos #5893
Labels
Component: Test Suite
Indicates an issue with the test framework or a test case
Status: Stale
No recent activity for issue
Comments
behlendorf
added
the
Component: Test Suite
Indicates an issue with the test framework or a test case
label
Mar 14, 2017
behlendorf
added a commit
to behlendorf/zfs
that referenced
this issue
May 1, 2017
The following three test cases occasionally fail the automated testing. For the moment disable these test cases until the underlying issues can be fully investigated and resolved. zfs_destroy_010_pos - openzfs#5893 rsend_020_pos - openzfs#6086 (32-bit only) send-c_volume - openzfs#6087 (32-bit only) Signed-off-by: Brian Behlendorf <[email protected]>
behlendorf
added a commit
to behlendorf/zfs
that referenced
this issue
May 1, 2017
The following three test cases occasionally fail the automated testing. For the moment disable these test cases until the underlying issues can be fully investigated and resolved. zfs_destroy_010_pos - openzfs#5893 rsend_020_pos - openzfs#6086 (32-bit only) send-c_volume - openzfs#6087 (32-bit only) Signed-off-by: Brian Behlendorf <[email protected]> Issue openzfs#5893 Issue openzfs#6086 Issue openzfs#6087
behlendorf
added a commit
to behlendorf/zfs
that referenced
this issue
May 2, 2017
* zfs_destroy_001_pos - Unable to reproduce the failures locally. Re-enabled to determine observed buildbot failure rate. * zfs_destroy_005_neg - Updated for expected Linux behavior. Busy mount points, even snapshots, are expected to fail. * zfs_destroy_010_pos - Resolved transient EBUSY with retry. Signed-off-by: Brian Behlendorf <[email protected]> Issue openzfs#5635 Issue openzfs#5893
behlendorf
added a commit
that referenced
this issue
May 4, 2017
* zfs_destroy_001_pos - Unable to reproduce the failures locally. Re-enabled to determine observed buildbot failure rate. * zfs_destroy_005_neg - Updated for expected Linux behavior. Busy mount points, even snapshots, are expected to fail. * zfs_destroy_010_pos - Resolved transient EBUSY with retry. Reviewed-by: Giuseppe Di Natale <[email protected]> Reviewed-by: George Melikov <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Issue #5635 Issue #5893 Closes #6091
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
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
Status: Stale
No recent activity for issue
System information
Describe the problem you're observing
Rare failure of test case zfs_destroy_010_pos due to an EBUSY error.
Describe how to reproduce the problem
Reproducible occasionally by the automated testing.
Include any warning/errors/backtraces from the system logs
http://build.zfsonlinux.org/builders/Ubuntu%2016.04%20x86_64%20Kmemleak%20%28TEST%29/builds/942/steps/shell_9/logs/log
The text was updated successfully, but these errors were encountered: