qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "John Snow" <jsnow@redhat.com>, "Cleber Rosa" <crosa@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Cc: kwolf@redhat.com, Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [PATCH v3 0/3] python/machine.py: refactor shutdown
Date: Mon, 22 Jun 2020 20:28:20 +0200	[thread overview]
Message-ID: <494f45f1-0379-04a3-39e4-f89bad42c4de@redhat.com> (raw)
In-Reply-To: <b6adbb99-e166-1c79-7282-cd9c713c6731@redhat.com>

+Alex

On 6/22/20 8:08 PM, John Snow wrote:
> On 6/22/20 1:55 PM, Philippe Mathieu-Daudé wrote:
>> On 6/22/20 7:51 PM, John Snow wrote:
>>>
>>>
>>> On 6/20/20 6:14 AM, Philippe Mathieu-Daudé wrote:
>>>> Still doesn't work...
>>>> https://travis-ci.org/github/philmd/qemu/jobs/700309163#L5445
>>>
>>> I tried running from master with just these patches applied. So far, the
>>> only failures I am seeing on gitlab/travis are job timeouts.
>>>
>>> Are you doing something special to avoid timeout failures?
>>
>> Unfortunately no :S Cleber tried too and couldn't reproduce,
>> I'm the only one lucky enough to win the race condition...
>>
>> Retrying the acceptance tests on Travis-CI is painful, yes,
>> I know...
>>
> 
> You didn't address the timeouts I asked about. Are you not seeing job
> timeouts? How is the CI passing at all, for anyone?
> 
> We seem to have bigger problems here.

OK, your problem/question was not obvious.

What helped me to is to know you setup'd your Travis-CI
account today.
At some point the jobs were taking too long, by caching
the ccache directory between runs, we could get quicker
builds.

My guess is as your setup is new, your cache is empty,
and you are reaching the 50min timeout...

If this is the case, I'm not sure how to resolve this.
Retry and retry again?



  reply	other threads:[~2020-06-22 18:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 19:52 [PATCH v3 0/3] python/machine.py: refactor shutdown John Snow
2020-06-04 19:52 ` [PATCH v3 1/3] python/machine.py: consolidate _post_shutdown() John Snow
2020-06-04 19:52 ` [PATCH v3 2/3] python/machine.py: refactor shutdown John Snow
2020-06-04 19:52 ` [PATCH v3 3/3] python/machine.py: re-add sigkill warning suppression John Snow
2020-06-05  9:34 ` [PATCH v3 0/3] python/machine.py: refactor shutdown Kevin Wolf
2020-06-09 13:08 ` Philippe Mathieu-Daudé
2020-06-09 21:55   ` John Snow
2020-06-15 15:21     ` Philippe Mathieu-Daudé
2020-06-15 22:21       ` Eduardo Habkost
2020-06-16 15:06         ` John Snow
2020-06-16 15:36           ` Philippe Mathieu-Daudé
2020-06-16 21:49       ` Cleber Rosa
2020-06-17 17:13         ` Philippe Mathieu-Daudé
2020-06-20 10:14           ` Philippe Mathieu-Daudé
2020-06-22 17:51             ` John Snow
2020-06-22 17:55               ` Philippe Mathieu-Daudé
2020-06-22 18:08                 ` John Snow
2020-06-22 18:28                   ` Philippe Mathieu-Daudé [this message]
2020-06-26 17:28             ` John Snow
2020-06-17 17:15 ` Philippe Mathieu-Daudé

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=494f45f1-0379-04a3-39e4-f89bad42c4de@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@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).