From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Yonggang Luo <luoyonggang@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"QEMU Trivial" <qemu-trivial@nongnu.org>,
qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH 2/2] cirrus: Fixing and speedup the msys2/mingw CI
Date: Wed, 7 Oct 2020 09:29:51 +0100 [thread overview]
Message-ID: <20201007082951.GE2505881@redhat.com> (raw)
In-Reply-To: <20201007024135.1885-3-luoyonggang@gmail.com>
These kind of changes are not appropriate for QEMU trivial.
On Wed, Oct 07, 2020 at 10:41:35AM +0800, Yonggang Luo wrote:
> Using a prepared https://github.com/lygstate/qemu/releases/download/v5.1.0/msys2-x86_64.tar.xz
> for speed up the msys2/mingw prepare speed on the cirrus CI.
I appreciate the desire to speed up CI, but relying on the contents of
a arbitrary blob provided by a user as the build environment is not
satisfatory for QEMU's CI. The project has no visibility, control
or tracking over what is in that blob.
Any caches need to be managed by the CI system, and populated by
the defined CI job logic.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2020-10-07 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 2:41 [PATCH 0/2] Improve cirrus msys2 Yonggang Luo
2020-10-07 2:41 ` [PATCH 1/2] docker: Add win32/msys2/mingw64 docker Yonggang Luo
2020-10-07 6:43 ` Thomas Huth
2020-10-07 8:17 ` 罗勇刚(Yonggang Luo)
2020-10-07 2:41 ` [PATCH 2/2] cirrus: Fixing and speedup the msys2/mingw CI Yonggang Luo
2020-10-07 8:29 ` Daniel P. Berrangé [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=20201007082951.GE2505881@redhat.com \
--to=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=luoyonggang@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.