qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Cleber Rosa" <crosa@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	Willian Rampazzo <wrampazz@redhat.com>,
	qemu-devel@nongnu.org,
	Wainer dos Santos Moschetta <wainersm@redhat.com>,
	Beraldo Leal <bleal@redhat.com>
Subject: Re: [PATCH 0/1] Acceptance Tests: bump Avocado version requirement to 87.0
Date: Mon, 3 May 2021 10:40:31 +0200	[thread overview]
Message-ID: <d80ec7d1-2c3d-5642-0459-9cbd3fff467d@redhat.com> (raw)
In-Reply-To: <262314931.15107240.1620006623468.JavaMail.zimbra@redhat.com>

On 5/3/21 3:50 AM, Cleber Rosa wrote:
> ----- Original Message -----
>> From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
>> On 4/14/21 6:11 PM, Cleber Rosa wrote:
>>> This is being proposed as a separate single patch simply to show
>>> that no known regressions have been introduced as far as the
>>> acceptance tests/jobs are related.  CI job:
>>>
>>>    https://gitlab.com/cleber.gnu/qemu/-/pipelines/286347312
>>>
>>> This version (and 86.0) contain improvements that address specific
>>> QEMU use cases, including:
>>>
>>>  * Fix to the error message given when downloading assets
>>>
>>>  * Asset listing/purging capabilities
>>>
>>> Cleber Rosa (1):
>>>   Acceptance Tests: bump Avocado version requirement to 87.0
>>>
>>>  tests/requirements.txt | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>
>> Ping? This patch should fix the mainstream pipeline error:
>> https://gitlab.com/qemu-project/qemu/-/jobs/1229752162
>>
> 
> Hi Phil,
> 
> I'll send with my python-next (and other) patches to be queued in a day
> or two... but the bad news is: I don't think Avocado 87.0 has the fix for
> the pipeline issue above.  I looked at the test log, and the kernel boot
> hangs right after:
> 
> 11:43:53 DEBUG| Freeing unused kernel memory: 1176K
> 11:43:53 DEBUG| This architecture does not have kernel memory protection.
> 
> And then gets interrupted by Avocado some 90 seconds after that.  I'll try
> to reproduce it and debug.

Oh, there was 2 errors... I just looked at the first one. Thanks for
being cautious with the test logs :)

Thomas / Alex, what do you suggest we do with the test_or1k_sim
timeouting? This is not the first time:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg781695.html

> 
>> (see
>> https://www.mail-archive.com/qemu-devel@nongnu.org/msg794416.html)
>>
>>
> 
> Avocado 87.0 does fix the issue you referenced here though.
> 
> Regards,
> - Cleber.
> 



      reply	other threads:[~2021-05-03  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 16:11 [PATCH 0/1] Acceptance Tests: bump Avocado version requirement to 87.0 Cleber Rosa
2021-04-14 16:11 ` [PATCH 1/1] " Cleber Rosa
2021-04-14 16:54   ` Wainer dos Santos Moschetta
2021-04-19 16:08   ` Willian Rampazzo
2021-05-02 15:24 ` [PATCH 0/1] " Philippe Mathieu-Daudé
2021-05-03  1:50   ` Cleber Rosa
2021-05-03  8:40     ` 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=d80ec7d1-2c3d-5642-0459-9cbd3fff467d@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=wrampazz@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).