All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Help improve 32-bit testing
Date: Tue, 25 Jun 2024 15:54:57 +0100	[thread overview]
Message-ID: <87le2toywu.fsf@draig.linaro.org> (raw)
In-Reply-To: <ab8beba8-658a-4359-bfb1-672e5782633d@linaro.org> (Richard Henderson's message of "Mon, 24 Jun 2024 16:33:08 -0700")

Richard Henderson <richard.henderson@linaro.org> writes:

> Hiya,
>
> I've just discovered a 32-bit build issue that is probably 3 weeks old.
>
> While we still support 32-bit builds at all, I would request that we
> improve our cross-i686 testing.  For instance: we have cross-i686-user
> and cross-i686-tci.  There is some system build testing in the tci
> job, but (rightfully) not everything.
>
> I would like a full cross-i686-system target that builds all targets,
> and I would like the debian-i686-cross image on which we base these to
> be more complete -- ideally, exactly matching x86_64.  In particular,
> CONFIG_SEV is not detected within the current docker image, which is
> where the current build error is located.
>
> Do you have time to look at this?

See:

  Subject: [RFC PATCH] testing: restore some testing for i686
  Date: Tue, 25 Jun 2024 15:54:18 +0100
  Message-Id: <20240625145418.694476-1-alex.bennee@linaro.org>

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      parent reply	other threads:[~2024-06-25 14:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24 23:33 Help improve 32-bit testing Richard Henderson
2024-06-25  7:11 ` Thomas Huth
2024-06-25 14:06   ` Richard Henderson
2024-06-25  7:49 ` Daniel P. Berrangé
2024-06-25  7:57 ` Philippe Mathieu-Daudé
2024-06-25 14:12   ` Richard Henderson
2024-06-25 14:54 ` Alex Bennée [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=87le2toywu.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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.