From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Cleber Rosa <crosa@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Aleksandar Rikalo" <arikalo@wavecomp.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: [Qemu-devel] [PULL 0/2] Python queue, 2019-06-18
Date: Tue, 18 Jun 2019 11:40:11 -0300 [thread overview]
Message-ID: <20190618144013.6537-1-ehabkost@redhat.com> (raw)
The following changes since commit cdfaa2720f4a09e5254868bd1f6e33f3e9eae76f:
Merge remote-tracking branch 'remotes/armbru/tags/pull-monitor-2019-06-17-v2' into staging (2019-06-18 10:47:00 +0100)
are available in the Git repository at:
git://github.com/ehabkost/qemu.git tags/python-next-pull-request
for you to fetch changes up to c21f30ebc779cd4210b488dd702b3f8653aee82b:
Travis: print acceptance tests logs in case of job failure (2019-06-18 11:15:08 -0300)
----------------------------------------------------------------
Python queue, 2019-06-18
Use a different method to dump avocado job log, to work around
timing-dependent issues in the arm test cases.
----------------------------------------------------------------
Cleber Rosa (1):
Travis: print acceptance tests logs in case of job failure
Eduardo Habkost (1):
Revert "travis: Make check-acceptance job more verbose"
.travis.yml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
2.18.0.rc1.1.g3f1ff2140
next reply other threads:[~2019-06-18 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 14:40 Eduardo Habkost [this message]
2019-06-18 14:40 ` [Qemu-devel] [PULL 1/2] Revert "travis: Make check-acceptance job more verbose" Eduardo Habkost
2019-06-18 14:40 ` [Qemu-devel] [PULL 2/2] Travis: print acceptance tests logs in case of job failure Eduardo Habkost
2019-06-18 15:50 ` [Qemu-devel] [PULL 0/2] Python queue, 2019-06-18 Peter Maydell
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=20190618144013.6537-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=amarkovic@wavecomp.com \
--cc=arikalo@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=crosa@redhat.com \
--cc=fam@euphon.net \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@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).