From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>, "Fam Zheng" <famz@redhat.com>,
qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: [Qemu-devel] [RFC PATCH RESEND 2/2] travis: use console aliveness script
Date: Thu, 13 Jul 2017 07:03:11 -0300 [thread overview]
Message-ID: <20170713100311.20037-3-f4bug@amsat.org> (raw)
In-Reply-To: <20170713100311.20037-1-f4bug@amsat.org>
Travis CI has specific time limits for each job, and will stop the build and
add an error message to the build log in the following situation[s]:
- A job produces no log output for 10 minutes
See: https://docs.travis-ci.com/user/customizing-the-build#build-timeouts
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index 27a2d9cfb3..032d111bb4 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -45,7 +45,7 @@ notifications:
on_failure: always
env:
global:
- - TEST_CMD="make check"
+ - TEST_CMD="scripts/aliveness.sh 69 make check"
matrix:
- CONFIG=""
- CONFIG="--enable-debug --enable-debug-tcg --enable-trace-backends=log"
--
2.13.2
prev parent reply other threads:[~2017-07-13 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 10:03 [Qemu-devel] [RFC PATCH RESEND 0/2] avoid Travis CI "no log output for 10 minutes" failure Philippe Mathieu-Daudé
2017-07-13 10:03 ` [Qemu-devel] [RFC PATCH RESEND 1/2] scripts: helper to keep console alive Philippe Mathieu-Daudé
2017-07-13 11:38 ` Eric Blake
2017-07-13 10:03 ` Philippe Mathieu-Daudé [this message]
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=20170713100311.20037-3-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=alex.bennee@linaro.org \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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).