All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: osstest service owner <osstest-admin@xenproject.org>,
	xen-devel@lists.xenproject.org
Subject: Re: [xen-unstable test] 187507: regressions - FAIL
Date: Fri, 6 Sep 2024 12:46:08 +0200	[thread overview]
Message-ID: <cd1049b1-e52a-4062-b106-e85bc8b56d76@suse.com> (raw)
In-Reply-To: <779f69aa-f1d3-4582-b08d-83f92d4614c2@citrix.com>

On 06.09.2024 12:07, Andrew Cooper wrote:
> On 06/09/2024 11:01 am, Andrew Cooper wrote:
>> On 06/09/2024 7:08 am, Jan Beulich wrote:
>>> On 06.09.2024 06:41, osstest service owner wrote:
>>>> flight 187507 xen-unstable real [real]
>>>> http://logs.test-lab.xenproject.org/osstest/logs/187507/
>>>>
>>>> Regressions :-(
>>>>
>>>> Tests which did not succeed and are blocking,
>>>> including tests which could not be run:
>>>>  build-i386-xsm                6 xen-build                fail REGR. vs. 187498
>>>>  build-i386                    6 xen-build                fail REGR. vs. 187498
>>> This is a result of "x86emul: introduce a struct cpu_policy * local in
>>> x86_emulate()", and me not noticing the issue because in my tree (for
>>> AMX in particular) I have several more uses of the variable. I'd really
>>> like to avoid undoing the change, but adding __maybe_unused also seems
>>> bogus to me, as does adding a seemingly stray (void)cp somewhere. Good
>>> alternative ideas, anyone?
>> __maybe_unused as at least accurate, and its less fragile than a (void)cp;
> 
> Interestingly, Gitlab's x86_32 build test missed this.
> 
> https://gitlab.com/xen-project/people/andyhhp/xen/-/jobs/7762103169 passed.
> 
> I wonder if there's anything we should have done to get better coverage.

From the build log:

make -C x86_emulator install
make[6]: Entering directory '/builds/xen-project/people/andyhhp/xen/tools/tests/x86_emulator'
make[6]: Nothing to be done for 'install'.
make[6]: Leaving directory '/builds/xen-project/people/andyhhp/xen/tools/tests/x86_emulator'

Iirc one of your colleagues (Alejandro?) had a patch to actually install the
test harness binary. I didn't like this very much, but the above may be a
good reason to have it despite my slight dislike. And I think I had indicated
already that if everyone else thinks this wants installing, so be it.

Jan


  reply	other threads:[~2024-09-06 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06  4:41 [xen-unstable test] 187507: regressions - FAIL osstest service owner
2024-09-06  6:08 ` Jan Beulich
2024-09-06 10:01   ` Andrew Cooper
2024-09-06 10:07     ` Andrew Cooper
2024-09-06 10:46       ` Jan Beulich [this message]
2024-09-06 12:41       ` Anthony PERARD

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=cd1049b1-e52a-4062-b106-e85bc8b56d76@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=osstest-admin@xenproject.org \
    --cc=xen-devel@lists.xenproject.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.