Skip to content
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_006_neg #5657

Closed
behlendorf opened this issue Jan 25, 2017 · 2 comments
Closed

Test case: history_006_neg #5657

behlendorf opened this issue Jan 25, 2017 · 2 comments
Labels
Component: Test Suite Indicates an issue with the test framework or a test case Status: Stale No recent activity for issue

Comments

@behlendorf
Copy link
Contributor

System information

Type Version/Name
Distribution Name all
Distribution Version all
Linux Kernel all
Architecture all
ZFS Version 0.7.0-rc3
SPL Version 0.7.0-rc3

Describe the problem you're observing

Rarely observed failure of history_006_neg 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

Test: /usr/share/zfs/zfs-tests/tests/functional/history/history_006_neg (run as root) [00:00] [FAIL]
00:50:39.31 ASSERTION: Verify 'zfs list|get|holds|mount|unmount|share|unshare|send'  will not be logged.
00:50:39.32 SUCCESS: /sbin/zfs snapshot testpool.27588/testfs.27588@snap1
00:50:39.33 SUCCESS: /sbin/zfs hold tag testpool.27588/testfs.27588@snap1
00:50:39.34 SUCCESS: /sbin/zfs snapshot testpool.27588/testfs.27588@snap2
00:50:39.35 SUCCESS: eval /sbin/zpool history testpool.27588 > /tmp/old_history.9025
00:50:39.37 SUCCESS: /sbin/zfs unmount testpool.27588/testfs.27588
00:50:39.38 SUCCESS: /sbin/zfs mount testpool.27588/testfs.27588
00:50:39.39 NAME                               TAG  TIMESTAMP
00:50:39.39 testpool.27588/testfs.27588@snap1  tag  Wed Jan 25  0:50 2017
00:50:39.39 SUCCESS: /sbin/zfs holds testpool.27588/testfs.27588@snap1
00:50:39.40 SUCCESS: eval /sbin/zpool history testpool.27588 > /tmp/new_history.9025
00:50:39.40 305a306
00:50:39.40 > 2017-01-25.00:50:39 zfs get mountpoint testpool.27588/testfs.27588
00:50:39.41 
00:50:39.41 ERROR: /usr/bin/diff /tmp/old_history.9025 /tmp/new_history.9025 exited 1
00:50:39.41 NOTE: Performing local cleanup via log_onexit (cleanup)
00:50:39.41 cannot destroy snapshot testpool.27588/testfs.27588@snap1: dataset is busy
00:50:39.41 ERROR: /sbin/zfs destroy -rf testpool.27588/testfs.27588 exited 1
@behlendorf 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 <[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
@behlendorf
Copy link
Contributor Author

Test: /usr/share/zfs/zfs-tests/tests/functional/history/history_006_neg (run as root) [00:00] [FAIL]
07:07:57.44 ASSERTION: Verify 'zfs list|get|holds|mount|unmount|share|unshare|send'  will not be logged.
07:07:57.49 SUCCESS: zfs snapshot testpool/testfs@snap1
07:07:57.54 SUCCESS: zfs hold tag testpool/testfs@snap1
07:07:57.60 SUCCESS: zfs snapshot testpool/testfs@snap2
07:07:57.64 SUCCESS: eval zpool history testpool > /tmp/old_history.23797
07:07:57.66 SUCCESS: zfs unmount testpool/testfs
07:07:57.68 SUCCESS: zfs mount testpool/testfs
07:07:57.70 NAME                   TAG  TIMESTAMP
07:07:57.70 testpool/testfs@snap1  tag  Sat May 20  7:07 2017
07:07:57.70 SUCCESS: zfs holds testpool/testfs@snap1
07:07:57.74 SUCCESS: eval zpool history testpool > /tmp/new_history.23797
07:07:57.74 305a306
07:07:57.74 > 2017-05-20.07:07:57 zfs list testpool/testfs
07:07:57.74 
07:07:57.74 ERROR: diff /tmp/old_history.23797 /tmp/new_history.23797 exited 1

@stale
Copy link

stale bot commented Aug 25, 2020

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.

@stale stale bot added the Status: Stale No recent activity for issue label Aug 25, 2020
@stale stale bot closed this as completed Nov 23, 2020
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
Projects
None yet
Development

No branches or pull requests

1 participant