Project

General

Profile

Actions

Bug #2386

closed

xfstests: failed #34

Added by Sage Weil almost 12 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Q/A
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

2012-05-06T12:46:21.380 INFO:teuthology.orchestra.run.out:034    [failed, exit status 1] - output mismatch (see 034.out.bad)
2012-05-06T12:46:21.384 INFO:teuthology.orchestra.run.out:--- 034.out   2012-05-06 15:35:34.442861428 -0400
2012-05-06T12:46:21.384 INFO:teuthology.orchestra.run.out:+++ 034.out.bad       2012-05-06 15:46:21.359580573 -0400
2012-05-06T12:46:21.384 INFO:teuthology.orchestra.run.out:@@ -1,5 +1,5 @@
2012-05-06T12:46:21.384 INFO:teuthology.orchestra.run.out: QA output created by 034
2012-05-06T12:46:21.384 INFO:teuthology.orchestra.run.out: *** init FS
2012-05-06T12:46:21.384 INFO:teuthology.orchestra.run.out: *** test
2012-05-06T12:46:21.384 INFO:teuthology.orchestra.run.out:-*** done
2012-05-06T12:46:21.384 INFO:teuthology.orchestra.run.out:+!!! failed to run xfsctl test program
2012-05-06T12:46:21.385 INFO:teuthology.orchestra.run.out: *** unmount

ubuntu@teuthology:/a/nightly_coverage_2012-05-06-b/741

Actions #1

Updated by Sage Weil almost 12 years ago

  • Priority changed from Normal to High
Actions #2

Updated by Alex Elder almost 12 years ago

I've been trying to find out whether this is still a problem or
if it was transient. But teuthology has had a string of
somewhat flaky results in the past week and I haven't quickly
found evidence of the the rbd.xfstests task even running.

The message reported here is a result of this block of code:

if ! src/xfsctl $SCRATCH_MNT $SCRATCH_MNT/fish >>$seq.full 2>&1
then
echo "!!! failed to run xfsctl test program"
exit
fi

The program "src/xfsctl" is a program found under the xfstests
directory, which gets installed for this test in /var/lib/xfstests.
The message would get displayed (and put the error output into the
"full" output file) if the program didn't exist, or if it did
exist but produced a non-zero exit code. The only way to tell
the difference would be to look at the "full" output file, which
at this point we do not save.

If something went wrong with the build stage of the xfstests then
the program might not exist.

If the program existed and ran, it could fail with non-zero status
if any of these occurred:
- open(${SCRATCH_MNT}, O_RDONLY) failed
- open(${SCRATCH_MNT}/fish, O_RDONLY) failed
- Any of the xfsctl() functions the test exercises produced an error

In any case, right now I just want to know whether we can close this
bug because it has disappeared. I will check back again later after
I get a little help with reviewing teuthology output.

Actions #3

Updated by Sage Weil over 11 years ago

  • Assignee deleted (Alex Elder)
Actions #4

Updated by Sage Weil over 11 years ago

  • Status changed from 12 to Resolved
Actions

Also available in: Atom PDF