xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: xen-devel@lists.xenproject.org
Cc: osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [xen-unstable-smoke test] 155811: regressions - FAIL
Date: Thu, 15 Oct 2020 10:31:28 +0200	[thread overview]
Message-ID: <06d74ec9-948c-dc89-10a3-171dd364e97f@suse.com> (raw)
In-Reply-To: <osstest-155811-mainreport@xen.org>

On 14.10.2020 22:41, osstest service owner wrote:
> flight 155811 xen-unstable-smoke real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/155811/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  build-amd64                   6 xen-build                fail REGR. vs. 155805

Looks like the changes to tools/include/xen/ population have
increased the chances of running into the race (or some similar
one) reported by Olaf in "races in toolstack build":

make[5]: Entering directory '/home/osstest/build.155810.build-amd64/xen/tools/include'
make -C xen-foreign
make[6]: Entering directory '/home/osstest/build.155810.build-amd64/xen/tools/include/xen-foreign'
mkdir -p xen/libelf acpi
ln -s /home/osstest/build.155810.build-amd64/xen/tools/include/../../xen/include/public/COPYING xen/
ln -s /home/osstest/build.155810.build-amd64/xen/tools/include/../../xen/include/public/*.h xen/
xg_main.c:52:10: fatal error: xen/sys/privcmd.h: No such file or directory
 #include <xen/sys/privcmd.h>
          ^~~~~~~~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/home/osstest/build.155810.build-amd64/xen/tools/debugger/gdbsx/xg/../../../../tools/Rules.mk:145: xg_main.o] Error 1
make[4]: *** Waiting for unfinished jobs....
ln -s /home/osstest/build.155810.build-amd64/xen/tools/include/../../xen/include/public/*/ xen/
ln -s ../xen-sys/Linux xen/sys

Obviously recursing into tools/include/ needs to precede any other
recursion underneath tools/. Or wait - this is a bogus 2nd recursion
into tools/include/, there's an appropriate one very early in the
build. I guess it's

make[4]: Leaving directory '/home/osstest/build.155810.build-amd64/xen/tools/debugger/gdbsx/gx'
make -C xg
make[4]: Entering directory '/home/osstest/build.155810.build-amd64/xen/tools/debugger/gdbsx/xg'
make -C ../../../include

Jan


      reply	other threads:[~2020-10-15  8:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 20:41 [xen-unstable-smoke test] 155811: regressions - FAIL osstest service owner
2020-10-15  8:31 ` Jan Beulich [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=06d74ec9-948c-dc89-10a3-171dd364e97f@suse.com \
    --to=jbeulich@suse.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 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).