qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Thomas Huth" <thuth@redhat.com>,
	qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Aurelien Jarno" <aurelien@aurel32.net>,
	"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 2/2] tests/functional: Mark the MIPS Debian Wheezy tests as flaky
Date: Fri, 31 Oct 2025 14:30:20 +0100	[thread overview]
Message-ID: <507f6a8f-6d1e-4146-b318-db342e870b3b@linaro.org> (raw)
In-Reply-To: <171d963f-9543-4a1d-9852-3ba48e9e7310@redhat.com>

On 31/10/25 12:33, Thomas Huth wrote:
> On 31/10/2025 10.41, Philippe Mathieu-Daudé wrote:
>> test_malta.py sometimes times out (likely hang) under GitLab CI:
>>
>>    1/57 qemu:func-thorough+func-mips-thorough+thorough / func-mips- 
>> malta    TIMEOUT   480.11s   killed by signal 15 SIGTERM
> 
> Do you have an URL from a test job where this happened? I clicked 
> through a bunch of failed pipelines in the qemu-project, but I only saw 
> failures of the replay test in recent runs...

I was thinking of https://gitlab.com/philmd/qemu/-/jobs/11869641060

▶  1/21 test_malta.MaltaMachineConsole.test_wheezy 
                    FAIL
  1/21 qemu:func-thorough+func-mips64el-thorough+thorough / 
func-mips64el-malta              ERROR           25.11s   exit status 1

2025-10-28 07:06:59,425: ^[[?25l^[[?1cSearching for RedBoot partition 
table in physmap-flash.0 at offset 0x1003f0000
2025-10-28 07:06:59,602: ^[7Creating 3 MTD partitions on "physmap-flash.0":
2025-10-28 07:06:59,603: 0x000000000000-0x000000100000 : "YAMON"
2025-10-28 07:06:59,605: 0x000000100000-0x0000003e0000 : "User FS"
2025-10-28 07:06:59,607: 0x0000003e0000-0x000000400000 : "Board Config"
2025-10-28 07:06:59,876: ^[[1G[^[[32m ok ^[[39;49mCPU 0 Unable to handle 
kernel paging request at virtual address 0000000000000028, epc == 
ffffffffc00ed234, ra == ffffffffc00ed210

Is it different that the GitLab issue report?

> 
> Also, does it happen for all mips targets, or only for specific flavors?

I can't tell so far.

> 
>   Thomas
> 



  reply	other threads:[~2025-10-31 13:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31  9:41 [PATCH 0/2] tests/functional: Disable flaky MIPS tests on our GitLab CI Philippe Mathieu-Daudé
2025-10-31  9:41 ` [PATCH 1/2] tests/functional: Mark the MIPS replay tests as flaky Philippe Mathieu-Daudé
2025-10-31 10:00   ` Richard Henderson
2025-10-31 10:19     ` Philippe Mathieu-Daudé
2025-10-31 11:16   ` Thomas Huth
2025-10-31  9:41 ` [PATCH 2/2] tests/functional: Mark the MIPS Debian Wheezy " Philippe Mathieu-Daudé
2025-10-31 11:33   ` Thomas Huth
2025-10-31 13:30     ` Philippe Mathieu-Daudé [this message]
2025-10-31 13:35       ` Philippe Mathieu-Daudé
2025-10-31 15:11       ` Thomas Huth
2025-10-31 10:00 ` [PATCH 0/2] tests/functional: Disable flaky MIPS tests on our GitLab CI Richard Henderson
2025-10-31 11:50   ` Richard Henderson
2025-10-31 11:00 ` 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=507f6a8f-6d1e-4146-b318-db342e870b3b@linaro.org \
    --to=philmd@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=berrange@redhat.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).