From: Ian Campbell <ian.campbell@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Subject: Re: [xen-unstable test] 79328: regressions - trouble: blocked/broken/fail/pass
Date: Fri, 29 Jan 2016 09:33:41 +0000 [thread overview]
Message-ID: <1454060021.28781.6.camel@citrix.com> (raw)
In-Reply-To: <osstest-79328-mainreport@xen.org>
On Fri, 2016-01-29 at 00:52 +0000, osstest service owner wrote:
> flight 79328 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/79328/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-amd64-rumpuserxen 5 rumpuserxen-build fail in 79178 REGR. vs. 79027
We force pushed 79027 because it failed build-{i386,amd64}-rumpuserxen.xen-
build with:
stunt ld: unknown option -rpath-link=/home/osstest/build.79027.build-amd64-rumpuserxen/xen/tools/xenstore/../../tools/libs/evtchn
Makefile:87: recipe for target 'xenstore-control' failed
In 79178 build-amd64-rumpuserxen.rumpuserxen-build, which is an earlier
step than xen-build, failed due to xenbits being out, so that is indeed a
"regression" vs 789027 even though 79027 was force pushed (because
regressions pay attention to steps).
Therefore I haven't force pushed this because we don't want to set a new
baseline of build-amd64-rumpuserxen.rumpuserxen-build failing, I don't
think. We will get a push eventually once it decides the failure in 79178
was spurious.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-01-29 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 0:52 [xen-unstable test] 79328: regressions - trouble: blocked/broken/fail/pass osstest service owner
2016-01-29 9:33 ` Ian Campbell [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=1454060021.28781.6.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.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).