From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, qemu-trivial@nongnu.org
Subject: [Qemu-devel] [PATCH] tests: Ignore fp test outputs
Date: Fri, 1 Feb 2019 13:32:34 -0600 [thread overview]
Message-ID: <20190201193234.20796-1-eblake@redhat.com> (raw)
Commit 2cade3d wired up new tests, but did not exclude the
new *.out files produced by running the tests.
Signed-off-by: Eric Blake <eblake@redhat.com>
---
tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/.gitignore b/tests/.gitignore
index 72c18aaab04..f2bf85c8c4c 100644
--- a/tests/.gitignore
+++ b/tests/.gitignore
@@ -5,6 +5,7 @@ benchmark-crypto-hmac
check-*
!check-*.c
!check-*.sh
+fp/*.out
qht-bench
rcutorture
test-*
--
2.20.1
next reply other threads:[~2019-02-01 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 19:32 Eric Blake [this message]
2019-02-01 20:13 ` [Qemu-devel] [PATCH] tests: Ignore fp test outputs Emilio G. Cota
2019-02-03 16:47 ` no-reply
2019-02-04 9:53 ` Alex Bennée
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=20190201193234.20796-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).