From: Ian Campbell <ian.campbell@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [xen-unstable test] 62646: tolerable FAIL - PUSHED
Date: Tue, 6 Oct 2015 16:31:08 +0100 [thread overview]
Message-ID: <1444145468.5302.223.camel@citrix.com> (raw)
In-Reply-To: <osstest-62646-mainreport@xen.org>
On Mon, 2015-10-05 at 18:21 +0000, osstest service owner wrote:
> flight 62646 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/62646/
>
> Failures :-/ but no regressions.
>
> Regressions which are regarded as allowable (not blocking):
> test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail like 62583
> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-localmigrate fail like 62583
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/ALL.html
paints a pretty sorry picture.
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm/ALL.html
is not a lot better, but does occasionally pass.
It seems as if both suffer quite badly in the migration test cases.
Both also suffer from issues with the install phase, but the test-amd64
-i386 case is much worse.
It looks as if the failures are mostly on italia* and merlot*, however that
might be somewhat down to the stickiness of failures.
By contrast the same test cases without stubdom appear to be in reasonable
shape (the odd failure, but nothing like as bad):
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm/ALL.html
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemut-debianhvm-amd64-xsm/ALL.html
This is hampered somewhat by the lack of logging of the guest serial when
stubdom is in use. For non-studom this ends up in the qemu log, for stubdom
I'm not sure which blackhole it goes down.
Ian.
next prev parent reply other threads:[~2015-10-06 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 18:21 [xen-unstable test] 62646: tolerable FAIL - PUSHED osstest service owner
2015-10-06 15:31 ` Ian Campbell [this message]
2015-10-07 9:34 ` [PATCH OSSTEST] stubdom: Arrange for guest serial to go to a host logfile Ian Campbell
2015-10-07 9:59 ` Ian Jackson
2015-10-07 10:58 ` [xen-unstable test] 62646: tolerable FAIL - PUSHED Ian Campbell
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=1444145468.5302.223.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=wei.liu2@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).