Project

General

Profile

Actions
Copy link

Bug #44114

open

test_cephfs_shell.TestDU test fail unexpectedly

Added by Rishabh Dave about 4 years ago. Updated about 4 years ago.

Status:
Need More Info
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I suspect it's because one of the test machines was pretty laggy. This has been reported multiple times before -

https://github.com/ceph/ceph/pull/32612#issuecomment-578825885
https://github.com/ceph/ceph/pull/32612#issuecomment-584572441
https://github.com/ceph/ceph/pull/32612#issuecomment-585168097
https://github.com/ceph/ceph/pull/32111#issuecomment-564691007

Actions
Copy link
 #1

Updated by Patrick Donnelly about 4 years ago

  • Status changed from New to Need More Info

Is this not related to your PR? I have not seen this in my testing.

Actions
Copy link
 #2

Updated by Rishabh Dave about 4 years ago

Nope, none of my recent PRs modify anything around TestDU. Besides, after splitting this PR I couldn't reproduce this issue at all. I suspect this happens whenever the waiting time for tests is high.

Actions
Copy link
 #3

Updated by Rishabh Dave about 4 years ago

Facing same failure again - https://github.com/ceph/ceph/pull/32288#issuecomment-606488282. In contrast the test passed locally -

2020-03-31 14:22:48,323.323 INFO:__main__:Running ['./bin/ceph', 'log', 'Ended test tasks.cephfs.test_cephfs_shell._TestDU.test_du_works_recursively_with_no_path_in_args']
2020-03-31 14:22:49,220.220 INFO:__main__:test_du_works_recursively_with_no_path_in_args (tasks.cephfs.test_cephfs_shell._TestDU) ... ok
2020-03-31 14:22:49,221.221 INFO:__main__:Stopped test: test_du_works_recursively_with_no_path_in_args (tasks.cephfs.test_cephfs_shell._TestDU) in 48.335915s
2020-03-31 14:22:49,221.221 INFO:__main__:
2020-03-31 14:22:49,221.221 INFO:__main__:----------------------------------------------------------------------
2020-03-31 14:22:49,221.221 INFO:__main__:Ran 1 test in 48.336s
2020-03-31 14:22:49,221.221 INFO:__main__:
2020-03-31 14:22:49,221.221 INFO:__main__:OK

Perhaps, what we need to do is add time.sleep(5) in these tests.

Actions
Copy link

Also available in: Atom PDF