From: Luis Chamberlain <mcgrof@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: fstests: cannot allocate memory - false negatives xfs/059
Date: Wed, 24 Jul 2019 01:52:46 +0000 [thread overview]
Message-ID: <20190724015246.GR30113@42.do-not-panic.com> (raw)
I'm seeing at least one test fail but in reality it doesn't
seem like a real failure, only memory pressure for a small
period of time, and the test actually passed. But it failed
since there was a difference in output.
I see this has been discussed but the emails date back years ago
and then refer to discussions using a URL which no longer exists.
As such I cannot determine what the conclusion was.
For example, the test below actually is fine, but just because it
display two extra lines of "Cannot allocate memory" its reported as a
failure.
What was the agreement to deal with this? Was there any? If no
agreement was reached, what about just excluding these lines from
the output, or modifying the utilities to not display such messages
unless a verbsose flag was passed.
I tried looking for xfsrestore to see where this would be coming from
and don't see that... so again.. still not sure what to do yet.
Thoughts?
SECTION -- xfs_nocrc_512
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 oscheck-xfs-nocrc-512 4.19.58 #1 SMP Wed
Jul 17 06:37:34 UTC 2019
MKFS_OPTIONS -- -f -f -m crc=0,reflink=0,rmapbt=0, -i sparse=0, -b
size=512, /dev/loop5
MOUNT_OPTIONS -- /dev/loop5 /media/scratch
xfs/059 14s ... - output mismatch (see
/var/lib/xfstests/results/oscheck-xfs-nocrc-512/4.19.58/xfs_nocrc_512/xfs/059.out.bad)
--- tests/xfs/059.out 2019-07-17 06:53:54.439742882 +0000
+++
/var/lib/xfstests/results/oscheck-xfs-nocrc-512/4.19.58/xfs_nocrc_512/xfs/059.out.bad
2019-07-23 18:36:06.530062007 +0000
@@ -29,6 +29,8 @@
xfsrestore: using file dump (drive_simple) strategy
xfsrestore: using file dump (drive_simple)
strategy
xfsrestore: using file dump (drive_simple)
strategy
+ Cannot allocate memory
+ Cannot allocate memory
xfsrestore: restore complete:
SECS seconds elapsed
xfsrestore: Restore Status:
SUCCESS
...
(Run 'diff -u
/var/lib/xfstests/tests/xfs/059.out
/var/lib/xfstests/results/oscheck-xfs-nocrc-512/4.19.58/xfs_nocrc_512/xfs/059.out.bad'
to see the entire
diff)
Ran: xfs/059
Failures: xfs/059
Failed 1 of 1 tests
reply other threads:[~2019-07-24 1:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190724015246.GR30113@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.