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.

Sign up for GitHub

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

Jump to bottom

Test case history_004_pos #7026

Closed
behlendorf opened this issue Jan 9, 2018 · 1 comment
Closed

Test case history_004_pos #7026

behlendorf opened this issue Jan 9, 2018 · 1 comment
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 zfs-0.7.0-230-gb02beca
SPL Version 0.7

Describe the problem you're observing

Rarely observed failure of history_004_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%202%20x86_64%20Release%20%28TEST%29/builds/105/

Test: /usr/share/zfs/zfs-tests/tests/functional/history/history_004_pos (run as root) [00:04] [FAIL]
02:51:58.52 ASSERTION: 'zpool history' can cope with simultaneous commands.
02:52:01.35 umount: testpool/clone3: mountpoint not found
02:52:01.35 cannot unmount 'testpool/clone3': umount failed
02:52:01.55 cannot create 'testpool/clone3': dataset already exists
02:52:01.62 cannot promote 'testpool/clone3': not a cloned filesystem
02:52:01.66 cannot destroy 'testpool/testfs3': filesystem has children
02:52:01.66 use '-r' to destroy the following datasets:
02:52:01.66 testpool/testfs3@snap
02:52:01.81 cannot create 'testpool/testfs3': dataset already exists
02:52:01.92 cannot create snapshot 'testpool/testfs3@snap': dataset already exists
02:52:02.69 The entries count error: entry_count=297  orig_count = 103
02:52:02.69 NOTE: Performing test-fail callback (/usr/share/zfs/zfs-tests/callbacks/zfs_dbgmsg.ksh)
@behlendorf behlendorf added the Component: Test Suite Indicates an issue with the test framework or a test case label Jan 9, 2018
behlendorf added a commit to behlendorf/zfs that referenced this issue Jan 9, 2018
@behlendorf
Disable history_004_pos
42f176a 
Occasionally observed failure of history_004_pos due to the test
case not being 100% reliable.  In order to prevent false positives
disable this test case until it can be made reliable.

Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Issue openzfs#7026
@behlendorf behlendorf mentioned this issue Jan 9, 2018
Merged
13 tasks
behlendorf added a commit that referenced this issue Jan 10, 2018
@behlendorf
Disable history_004_pos
7e7f513 
Occasionally observed failure of history_004_pos due to the test
case not being 100% reliable.  In order to prevent false positives
disable this test case until it can be made reliable.

Reviewed-by: George Melikov <mail@gmelikov.ru>
Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Issue #7026 
Closes #7028
prometheanfire pushed a commit to prometheanfire/zfs that referenced this issue Jan 11, 2018
@behlendorf @prometheanfire
Disable history_004_pos
caca202 
Occasionally observed failure of history_004_pos due to the test
case not being 100% reliable.  In order to prevent false positives
disable this test case until it can be made reliable.

Reviewed-by: George Melikov <mail@gmelikov.ru>
Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Issue openzfs#7026 
Closes openzfs#7028
prometheanfire pushed a commit to prometheanfire/zfs that referenced this issue Jan 11, 2018
@behlendorf @prometheanfire
Disable history_004_pos
890c128 
Occasionally observed failure of history_004_pos due to the test
case not being 100% reliable.  In order to prevent false positives
disable this test case until it can be made reliable.

Reviewed-by: George Melikov <mail@gmelikov.ru>
Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Issue openzfs#7026 
Closes openzfs#7028
prometheanfire pushed a commit to prometheanfire/zfs that referenced this issue Jan 17, 2018
@behlendorf @prometheanfire
Disable history_004_pos
f4b5dd9 
Occasionally observed failure of history_004_pos due to the test
case not being 100% reliable.  In order to prevent false positives
disable this test case until it can be made reliable.

Reviewed-by: George Melikov <mail@gmelikov.ru>
Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Issue openzfs#7026 
Closes openzfs#7028
Nasf-Fan pushed a commit to Nasf-Fan/zfs that referenced this issue Jan 29, 2018
@behlendorf @Nasf-Fan
Disable history_004_pos
c908382 
Occasionally observed failure of history_004_pos due to the test
case not being 100% reliable.  In order to prevent false positives
disable this test case until it can be made reliable.

Reviewed-by: George Melikov <mail@gmelikov.ru>
Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Issue openzfs#7026
Closes openzfs#7028
Nasf-Fan pushed a commit to Nasf-Fan/zfs that referenced this issue Feb 13, 2018
@behlendorf @Nasf-Fan
Disable history_004_pos
a664430 
Occasionally observed failure of history_004_pos due to the test
case not being 100% reliable.  In order to prevent false positives
disable this test case until it can be made reliable.

Reviewed-by: George Melikov <mail@gmelikov.ru>
Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Issue openzfs#7026
Closes openzfs#7028
@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 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
1 participant
@behlendorf