From: Anthony PERARD <anthony.perard@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [qemu-upstream-unstable test] 116118: FAIL
Date: Mon, 13 Nov 2017 11:50:07 +0000 [thread overview]
Message-ID: <20171113115007.GA20656@perard.uk.xensource.com> (raw)
In-Reply-To: <osstest-116118-mainreport@xen.org>
On Mon, Nov 13, 2017 at 06:44:49AM +0000, osstest service owner wrote:
> flight 116118 qemu-upstream-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/116118/
>
> Failures and problems with tests :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-armhf-pvops <job status> broken in 115713
> build-armhf-pvops 4 host-install(4) broken in 115713 REGR. vs. 114457
This test pass in this flight. Why the fact that it was broken in an
older flight is blocking here?
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-11-13 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 6:44 [qemu-upstream-unstable test] 116118: FAIL osstest service owner
2017-11-13 11:50 ` Anthony PERARD [this message]
2017-11-13 11:52 ` Julien Grall
2017-11-13 11:53 ` Wei Liu
2017-11-13 11:58 ` Julien Grall
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=20171113115007.GA20656@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--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).