qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Djordje Todorovic <Djordje.Todorovic@htecgroup.com>,
	Alistair Francis <alistair23@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-riscv@nongnu.org" <qemu-riscv@nongnu.org>,
	"cfu@mips.com" <cfu@mips.com>, "mst@redhat.com" <mst@redhat.com>,
	"marcel.apfelbaum@gmail.com" <marcel.apfelbaum@gmail.com>,
	"dbarboza@ventanamicro.com" <dbarboza@ventanamicro.com>,
	"philmd@linaro.org" <philmd@linaro.org>
Subject: Re: [PATCH v1 0/1] riscv: Update MIPS vendor id
Date: Thu, 6 Nov 2025 11:46:12 +0100	[thread overview]
Message-ID: <c860c211-f0e2-442e-954b-cfeafca511b0@redhat.com> (raw)
In-Reply-To: <5301acd3-6e1e-41f0-9cf0-f262bd8c5521@htecgroup.com>

On 06/11/2025 11.16, Djordje Todorovic wrote:
> 
> On 5. 11. 25. 00:08, Alistair Francis wrote:
>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>
>>
>> On Wed, Nov 5, 2025 at 1:07 AM Djordje Todorovic
>> <Djordje.Todorovic@htecgroup.com> wrote:
>>> We have already sent patch set for introducing MIPS's
>>> p8700 CPU in qemu at:
>>>
>>>     https://patchew.org/QEMU/20251018154522.745788-1-djordje.todorovic@htecgroup.com/
>> That series was dropped as it failed to pass the CI tests:
>> https://patchew.org/QEMU/20251023041435.1775208-1-alistair.francis@wdc.com/
>>
>> You can just include this change in a new patchset
>>
>> Alistair
>>
> Hi Alistair,
> 
> 
> I am looking into the
> https://gitlab.com/qemu-project/qemu/-/jobs/11827080939#L5859
> 
> and it seems that it did not get the binaries from:
> 
> https://github.com/MIPS/linux-test-downloads/raw/main/p8700/fw_payload.bin
> 
> The test for Boston board should try to download that, but there is
> TIMEOUT set for it.

According to the job log, the test has been added to the "quick" category. 
If the test downloads assets, it has to be in the "thorough" category 
instead, otherwise you might run into timeouts when the download takes to 
long. (See also the "Asset handling" section in 
docs/devel/testing/functional.rst)

  HTH,
   Thomas



      reply	other threads:[~2025-11-06 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 15:07 [PATCH v1 0/1] riscv: Update MIPS vendor id Djordje Todorovic
2025-11-04 15:07 ` [PATCH v1 1/1] " Djordje Todorovic
2025-11-04 15:12   ` Daniel Henrique Barboza
2025-11-04 23:08 ` [PATCH v1 0/1] " Alistair Francis
2025-11-06 10:16   ` Djordje Todorovic
2025-11-06 10:46     ` Thomas Huth [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=c860c211-f0e2-442e-954b-cfeafca511b0@redhat.com \
    --to=thuth@redhat.com \
    --cc=Djordje.Todorovic@htecgroup.com \
    --cc=alistair23@gmail.com \
    --cc=cfu@mips.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@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).