Bug #4959
closedxfstest 17 failure
0%
Description
logs: ubuntu@teuthology:/a/teuthology-2013-05-08_01:00:26-rbd-master-testing-basic/8696
Traceback (most recent call last):
File "/var/lib/teuthworker/teuthology-master/teuthology/run_tasks.py", line 45, in run_tasks
suppress = manager.__exit__(*exc_info)
File "/usr/lib/python2.7/contextlib.py", line 24, in exit
self.gen.next()
File "/var/lib/teuthworker/teuthology-master/teuthology/task/qemu.py", line 317, in task
yield
File "/usr/lib/python2.7/contextlib.py", line 24, in exit
self.gen.next()
File "/var/lib/teuthworker/teuthology-master/teuthology/contextutil.py", line 35, in nested
if exit(*exc):
File "/usr/lib/python2.7/contextlib.py", line 24, in exit
self.gen.next()
File "/var/lib/teuthworker/teuthology-master/teuthology/task/qemu.py", line 227, in run_qemu
client=client
File "/var/lib/teuthworker/teuthology-master/teuthology/orchestra/remote.py", line 42, in run
r = self._runner(client=self.ssh, **kwargs)
File "/var/lib/teuthworker/teuthology-master/teuthology/orchestra/run.py", line 266, in run
r.exitstatus = _check_status(r.exitstatus)
File "/var/lib/teuthworker/teuthology-master/teuthology/orchestra/run.py", line 262, in _check_status
raise CommandFailedError(command=r.command, exitstatus=status, node=host)
CommandFailedError: Command failed on 10.214.132.23 with status 1: 'test -f /home/ubuntu/cephtest/8696/archive/qemu/client.0/success'
Updated by Tamilarasi muthamizhan almost 11 years ago
- Project changed from rgw to rbd
Updated by Josh Durgin almost 11 years ago
A single xfstest failed:
017 [failed, exit status 1] - output mismatch (see 017.out.bad)
--- 017.out 2013-05-08 08:58:37.602227034 +0000
+++ 017.out.bad 2013-05-08 09:03:46.762227034 +0000
@@ -6,5 +6,6 @@
*** test 2
*** test 3
*** test 4
-*** done
+DIRTY LOG
+(see 017.full for details)
*** unmount
Unfortunately we don't save the vm image, so we don't have 017.full.
Alex, does this kind of failure indicate a real issue, or just some rare circumstance that caused extra output not handled by xfstests?
Updated by Alex Elder almost 11 years ago
That's a really weird output.
The "*** test 3" (and 3 and 4) are shown at the top of a
loop that:
- runs fsstress on a mounted file system
- remounts the file system read-only
- prints the contents of the log (should be clean)
- runs a file system check
- remounts read-write for the next iteration
After all iterations are done, "*** done" gets printed.
The "DIRTY LOG" message gets printed by a "_check_log"
function that isn't even used in test 017 (directly).
Do we run tests concurrently here?
Updated by Josh Durgin almost 11 years ago
Whoops, meant to update this this morning. There's only one set of tests running, so no concurrency.
Updated by Josh Durgin almost 11 years ago
The same test failed again in the same way. This time rbd caching was enabled, while the first time it was disabled.
From /a/teuthology-2013-05-12_01:00:23-rbd-master-testing-basic/11767/remote/ubuntu@plana92.front.sepia.ceph.com/qemu/client.0/test.log:
017 [failed, exit status 1] - output mismatch (see 017.out.bad)
--- 017.out 2013-05-12 09:13:07.945152001 +0000
+++ 017.out.bad 2013-05-12 09:16:27.841152142 +0000
@@ -5,6 +5,6 @@
*** test 1
*** test 2
*** test 3
- *** test 4
-*** done
+DIRTY LOG
+(see 017.full for details)
Updated by Sage Weil almost 11 years ago
- Subject changed from rbd qemu test failure in the nightlies to xfstest 17 failure