qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org
Subject: Re: [PATCH] gitlab: Disable plugins for cross-i386-tci
Date: Fri, 30 Jun 2023 08:09:52 +0200	[thread overview]
Message-ID: <d66e6001-63d1-7307-66a8-4c48e11741ce@linaro.org> (raw)
In-Reply-To: <d09e7410-6bf9-e15b-5759-e111f60e9f19@redhat.com>

On 6/29/23 17:06, Thomas Huth wrote:
> On 29/06/2023 15.08, Richard Henderson wrote:
>> There are timeouts in the cross-i386-tci job that are related to plugins.
>> Restrict this job to basic TCI testing.
>>
>> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>> ---
>>
>> E.g. most recent failure(s),
>>
>> https://gitlab.com/qemu-project/qemu/-/jobs/4565517825
>> 4488: make[1]: *** [Makefile:189: run-plugin-memory-with-libbb.so] Error 124
>> 4497: make[1]: *** [Makefile:189: run-plugin-memory-with-libempty.so] Error 124
>> 4506: make[1]: *** [Makefile:189: run-plugin-memory-with-libinsn.so] Error 124
>> 4550: make[1]: *** [Makefile:189: run-plugin-memory-with-libmem.so] Error 124
>> 4558: make[1]: *** [Makefile:189: run-plugin-memory-with-libsyscall.so] Error 124
>>
>> We do tci+plugin testing with an x86_64 job, so I don't think it's
>> important that we cover plugins here.  Mostly we want to make sure
>> that TCI *builds* on a 32-bit host.
>>
>> Anyway, here's a pass with shared infrastructure,
>> https://gitlab.com/rth7680/qemu/-/jobs/4565547513
>>
>> There might well be different timings on the project k8s hosts.
>>
>>
>> r~
>>
>> ---
>>   .gitlab-ci.d/crossbuilds.yml | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/.gitlab-ci.d/crossbuilds.yml b/.gitlab-ci.d/crossbuilds.yml
>> index 1e0e6c7f2c..b6ec99ecd1 100644
>> --- a/.gitlab-ci.d/crossbuilds.yml
>> +++ b/.gitlab-ci.d/crossbuilds.yml
>> @@ -57,7 +57,7 @@ cross-i386-tci:
>>     variables:
>>       IMAGE: fedora-i386-cross
>>       ACCEL: tcg-interpreter
>> -    EXTRA_CONFIGURE_OPTS: 
>> --target-list=i386-softmmu,i386-linux-user,aarch64-softmmu,aarch64-linux-user,ppc-softmmu,ppc-linux-user
>> +    EXTRA_CONFIGURE_OPTS: 
>> --target-list=i386-softmmu,i386-linux-user,aarch64-softmmu,aarch64-linux-user,ppc-softmmu,ppc-linux-user --disable-plugins
>>       MAKE_CHECK_ARGS: check check-tcg
>>   cross-mipsel-system:
> 
> FWIW,
> Acked-by: Thomas Huth <thuth@redhat.com>
> 
> I assume you'll apply this directly as a CI fix?

Yes.  Now done.


r~



      reply	other threads:[~2023-06-30  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 13:08 [PATCH] gitlab: Disable plugins for cross-i386-tci Richard Henderson
2023-06-29 15:06 ` Thomas Huth
2023-06-30  6:09   ` Richard Henderson [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=d66e6001-63d1-7307-66a8-4c48e11741ce@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=qemu-devel@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 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).