From: Thomas Huth <thuth@redhat.com>
To: "Cédric Le Goater" <clg@kaod.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2 6/7] gitlab: build the correct microblaze target
Date: Mon, 4 Dec 2023 14:32:08 +0100 [thread overview]
Message-ID: <3fa71396-abbd-47e3-b9c5-a1c1eabcf7ac@redhat.com> (raw)
In-Reply-To: <3ae174c2-bad6-4099-8e39-a2f02f58cdfd@kaod.org>
On 04/12/2023 13.48, Cédric Le Goater wrote:
> On 12/4/23 13:43, Thomas Huth wrote:
>> On 04/12/2023 13.40, Alex Bennée wrote:
>>> Thomas Huth <thuth@redhat.com> writes:
>>>
>>>> On 01/12/2023 10.36, Alex Bennée wrote:
>>>>> We inadvertently built the LE target for BE tests.
>>>>> Fixes: 78ebc00b06 (gitlab: shuffle some targets and reduce avocado
>>>>> noise)
>>>>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>>>>> ---
>>>>> .gitlab-ci.d/buildtest.yml | 2 +-
>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
>>>>> index 7f9af83b10..62b5379a5e 100644
>>>>> --- a/.gitlab-ci.d/buildtest.yml
>>>>> +++ b/.gitlab-ci.d/buildtest.yml
>>>>> @@ -41,7 +41,7 @@ build-system-ubuntu:
>>>>> variables:
>>>>> IMAGE: ubuntu2204
>>>>> CONFIGURE_ARGS: --enable-docs
>>>>> - TARGETS: alpha-softmmu microblazeel-softmmu mips64el-softmmu
>>>>> + TARGETS: alpha-softmmu microblaze-softmmu mips64el-softmmu
>>>>> MAKE_CHECK_ARGS: check-build
>>>>> check-system-ubuntu:
>>>>
>>>> We've got microblazeel-softmmu here and microblaze-softmmu in the
>>>> build-system-fedora job. So please don't change the ubuntu job here,
>>>> otherwise we're building the same target twice instead.
>>>
>>> Hmm - what would be really useful is an actual microblazeel test image
>>> so we can test what we build.
>>
>> We've got at least a small test in tests/qtest/boot-serial-test.c, so we
>> know that at least some instructions can be executed via TCG.
>
> There are 2 configs under buildroot, qemu_microblazebe_mmu_defconfig and
> qemu_microblazeel_mmu_defconfig, we could possibly use.
I already used the big endian config for going shopping for ballerinas
(which we already use in one of the avocado tests):
http://www.qemu-advent-calendar.org/2018/#day-17
And as I just learnt today, the QEMU advent calendar opens its doors again
in 2023:
http://www.qemu-advent-calendar.org/2023/
Let's see, maybe we can have a nice surprise for microblazeel this time...
Thomas
next prev parent reply other threads:[~2023-12-04 13:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 9:36 [PATCH v2 0/7] final fixes for 8.2 Alex Bennée
2023-12-01 9:36 ` [PATCH v2 1/7] gdbstub: use a better signal when we halt for IO reasons Alex Bennée
2023-12-01 9:36 ` [PATCH v2 2/7] docs/devel: rationalise unstable gitlab tests under FLAKY_TESTS Alex Bennée
2023-12-01 9:36 ` [PATCH v2 3/7] tests/avocado: drop BootLinuxConsole.test_mips_malta_cpio test Alex Bennée
2023-12-01 11:27 ` Stefan Hajnoczi
2023-12-01 13:45 ` Philippe Mathieu-Daudé
2023-12-01 13:57 ` Philippe Mathieu-Daudé
2023-12-01 13:59 ` Philippe Mathieu-Daudé
2023-12-01 15:14 ` Alex Bennée
2023-12-01 9:36 ` [PATCH v2 4/7] tests/avocado: drop malta yamon tests Alex Bennée
2023-12-01 10:24 ` Philippe Mathieu-Daudé
2023-12-01 12:49 ` Alex Bennée
2023-12-01 13:22 ` Philippe Mathieu-Daudé
2023-12-01 14:05 ` Philippe Mathieu-Daudé
2023-12-01 15:16 ` Alex Bennée
2023-12-01 9:36 ` [PATCH v2 5/7] tests/avocado: tag sbsa tests as tcg only Alex Bennée
2023-12-01 10:26 ` Philippe Mathieu-Daudé
2023-12-01 9:36 ` [PATCH v2 6/7] gitlab: build the correct microblaze target Alex Bennée
2023-12-01 10:24 ` Philippe Mathieu-Daudé
2023-12-04 7:54 ` Thomas Huth
2023-12-04 12:40 ` Alex Bennée
2023-12-04 12:43 ` Thomas Huth
2023-12-04 12:48 ` Cédric Le Goater
2023-12-04 13:32 ` Thomas Huth [this message]
2023-12-01 9:36 ` [PATCH v2 7/7] gitlab: add optional job to run flaky avocado tests Alex Bennée
2023-12-01 10:28 ` Philippe Mathieu-Daudé
2023-12-01 13:30 ` [PATCH v2 0/7] final fixes for 8.2 Stefan Hajnoczi
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=3fa71396-abbd-47e3-b9c5-a1c1eabcf7ac@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=clg@kaod.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).