qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Ed Maste <emaste@freebsd.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3] .cirrus.yml: basic compile and test for FreeBSD
Date: Mon, 21 Jan 2019 15:36:43 +0000	[thread overview]
Message-ID: <877eey10qc.fsf@linaro.org> (raw)
In-Reply-To: <CAPyFy2CTXcq2ue7BVAHWeOtCh4+ovtKHvgMDoVhetNKdKRTSsQ@mail.gmail.com>


Ed Maste <emaste@freebsd.org> writes:

> On Mon, 21 Jan 2019 at 06:03, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> I should be able to add CirrusCI to the QEMU project github when we
>> merge. I see there is another revision coming in so I''ll wait for that
>> before I queue it up.
>
> Do you mean my eadd119 commit "cirrus: tail dmesg to see if this is
> due to OOM"? I didn't intend to submit that (at least not in exactly
> the current form); I added it while looking at what I believe was a
> transient Cirrus failure.

Ahh no - I thought Thomas had a failure with long build times. However
if it's a hanging test that goes away on retry it's good to go.

--
Alex Bennée

  reply	other threads:[~2019-01-21 15:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 19:19 [Qemu-devel] [PATCH v2] .cirrus.yml: basic compile and test for FreeBSD Ed Maste
2019-01-17  6:28 ` Thomas Huth
2019-01-18 14:41   ` Ed Maste
2019-01-18 14:47 ` [Qemu-devel] [PATCH v3] " emaste
2019-01-21  9:13   ` Thomas Huth
2019-01-21 10:18     ` Thomas Huth
2019-01-21 15:16       ` Ed Maste
2019-01-21 16:30         ` Ed Maste
2019-01-22  9:40           ` Thomas Huth
2019-01-22 10:41             ` Peter Maydell
2019-01-22 13:42             ` Ed Maste
2019-01-22 14:09               ` Thomas Huth
2019-01-21 11:03   ` Alex Bennée
2019-01-21 15:20     ` Ed Maste
2019-01-21 15:36       ` Alex Bennée [this message]
2019-01-23 10:58 ` [Qemu-devel] [PATCH v2] " no-reply

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=877eey10qc.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=emaste@freebsd.org \
    --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).