From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH] .travis.yml: Install python3-tomli in all build jobs
Date: Mon, 24 Jun 2024 12:31:44 +0200 [thread overview]
Message-ID: <a1ad5a7a-d299-4053-8cc9-b7d2c9c3fad6@redhat.com> (raw)
In-Reply-To: <87tthips8d.fsf@draig.linaro.org>
On 24/06/2024 12.09, Alex Bennée wrote:
> Thomas Huth <thuth@redhat.com> writes:
>
>> Since commit 1f97715c83 ('Revert "python: use vendored tomli"')
>> this package is a hard requirement for compiling QEMU, so install
>> it now in all Travis jobs, too.
>
> AFAICT the only repo currently running these tests is your github
> mirror:
>
> https://app.travis-ci.com/github/huth/qemu/builds?serverType=git
>
> Because both the official github mirror and the gitlab project haven't
> run anything for a while:
>
> https://app.travis-ci.com/gitlab/qemu-project/qemu/branches
> https://app.travis-ci.com/github/qemu/qemu/branches
AFAIK the gitlab integration broke completely at one point in time. But as
you can see with my account, it still works fine for the github repo - I
just need to write a short mail to the travis support once a year to ask
them to extend the open source credits for my repo. So apart from that minor
effort, it's a very convenient way to test QEMU on non-x86 hosts.
> FWIW the changes themselves look fine:
>
> Acked-by: Alex Bennée <alex.bennee@linaro.org>
Thanks!
Thomas
next prev parent reply other threads:[~2024-06-24 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 9:48 [PATCH] .travis.yml: Install python3-tomli in all build jobs Thomas Huth
2024-06-24 10:09 ` Alex Bennée
2024-06-24 10:31 ` Thomas Huth [this message]
2024-08-20 8:51 ` Stefan Weil via
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=a1ad5a7a-d299-4053-8cc9-b7d2c9c3fad6@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.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).