qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: berrange@redhat.com,
	"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH 0/2] dockerfiles, gitlab-ci: add CI job using nightly Rust
Date: Wed,  9 Oct 2024 11:01:48 +0200	[thread overview]
Message-ID: <20241009090151.1643088-1-pbonzini@redhat.com> (raw)

Right now only Fedora 39 and 40 (with updates) are able to compile
QEMU with Rust enabled. Full CI enablement requires further work to
reduce the minimum supported version of the compiler, and is not a
requirement until Rust is turned on by default.

Since a CI job based on nightly Rust will be needed later on, to
integrate clippy and have a heads-up on future clippy warnings,
adjust QEMU's 'refresh' script to customize a Fedora 40 dockerfile
with trailing text that installs nightly Rust and compiles the
latest bindgen.  A matching CI job, using --enable-rust, ensures
that the toolchain is installed correctly by the Dockerfile and
that QEMU builds with Rust enabled on at least one platform.

Suggested-by: Daniel P. Berrangé <berrange@redhat.com>
Cc: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Cc: Alex Bennée <alex.bennee@linaro.org>
Based-on: <cover.1727961605.git.manos.pitsidianakis@linaro.org>

v1->v2: remove unnecessary CONFIGURE_ARGS
        add "nightly" to name of container and job

Paolo Bonzini (2):
  dockerfiles: add a Dockerfile using a nightly Rust toolchain
  gitlab-ci: add Rust-enabled CI job

 .gitlab-ci.d/buildtest.yml                    |  13 ++
 .gitlab-ci.d/containers.yml                   |   6 +
 .../dockerfiles/fedora-rust-nightly.docker    | 173 ++++++++++++++++++
 tests/lcitool/refresh                         |  26 +++
 4 files changed, 218 insertions(+)
 create mode 100644 tests/docker/dockerfiles/fedora-rust-nightly.docker

-- 
2.46.2



             reply	other threads:[~2024-10-09  9:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  9:01 Paolo Bonzini [this message]
2024-10-09  9:01 ` [PATCH 1/2] dockerfiles: add a Dockerfile using a nightly Rust toolchain Paolo Bonzini
2024-10-09 12:55   ` Alex Bennée
2024-10-09  9:01 ` [PATCH 2/2] gitlab-ci: add Rust-enabled CI job Paolo Bonzini
2024-10-09  9:07   ` Daniel P. Berrangé
2024-10-09 12:55   ` Alex Bennée
  -- strict thread matches above, loose matches on Subject: below --
2024-10-07 17:17 [PATCH 0/2] dockerfiles, gitlab-ci: add CI job using nightly Rust Paolo Bonzini
2024-10-07 18:18 ` Daniel P. Berrangé
2024-10-08  9:03   ` Paolo Bonzini
2024-10-08  9:20     ` Daniel P. Berrangé
2024-10-08  9:45       ` Paolo Bonzini
2024-10-08  9:56         ` Daniel P. Berrangé

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=20241009090151.1643088-1-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=manos.pitsidianakis@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).