From: "Jan Beulich" <JBeulich@novell.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com
Subject: Re: [linux test] 7244: regressions - FAIL
Date: Mon, 23 May 2011 09:08:17 +0100 [thread overview]
Message-ID: <4DDA32110200007800042C55@vpn.id2.novell.com> (raw)
In-Reply-To: <osstest-7244-mainreport@xen.org>
>>> On 23.05.11 at 08:11, xen.org <ian.jackson@eu.citrix.com> wrote:
> flight 7244 linux real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/7244/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking:
> test-amd64-i386-pair 16 guest-start fail REGR. vs. 7062
> test-amd64-i386-pv 9 guest-start fail REGR. vs. 7062
> test-amd64-i386-xl-credit2 9 guest-start fail REGR. vs. 7062
> test-amd64-i386-xl-multivcpu 9 guest-start fail REGR. vs. 7062
> test-amd64-i386-xl 9 guest-start fail REGR. vs. 7062
> test-i386-i386-pair 16 guest-start fail REGR. vs. 7062
> test-i386-i386-pv 9 guest-start fail REGR. vs. 7062
> test-i386-i386-xl 9 guest-start fail REGR. vs. 7062
This failure pattern has been consistent for several days, and with
there being only two changes under test I would have though it
would be pretty obvious what the problem is (despite there not
being anything useful in the logs as far as I was able to see).
If it's non-obvious, shouldn't one of the two simply get reverted,
to determine which one is at fault? (I could imagine the blkback
change being the problematic one, as it so far didn't get replaced
by the more tolerant version that next-2.6.39 got meanwhile, in
particular because older Linux [before 2.6.24 I think] wasn't
even able to handle empty barrier requests.)
Jan
> Tests which are failing intermittently (not blocking):
> test-amd64-i386-rhel6hvm-amd 7 redhat-install fail pass in 7235
>
> Tests which did not succeed, but are not blocking,
> including regressions (tests previously passed) regarded as allowable:
> test-amd64-amd64-win 16 leak-check/check fail never pass
> test-amd64-amd64-xl-win 13 guest-stop fail never pass
> test-amd64-i386-rhel6hvm-intel 8 guest-saverestore fail never pass
> test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
> test-amd64-i386-win 16 leak-check/check fail never pass
> test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
> test-i386-i386-win 16 leak-check/check fail never pass
> test-i386-i386-xl-win 13 guest-stop fail never pass
>
> version targeted for testing:
> linux 78e7a0c14685d544453e85a331aa7f63831c2d3b
> baseline version:
> linux 2b494f184d3337d10d59226e3632af56ea66629a
>
> ------------------------------------------------------------
> People who touched revisions under test:
> ------------------------------------------------------------
>
> jobs:
> build-amd64 pass
> build-i386 pass
> build-amd64-pvops pass
> build-i386-pvops pass
> test-amd64-amd64-xl pass
> test-amd64-i386-xl fail
> test-i386-i386-xl fail
> test-amd64-i386-rhel6hvm-amd fail
> test-amd64-i386-xl-credit2 fail
> test-amd64-i386-rhel6hvm-intel fail
> test-amd64-i386-xl-multivcpu fail
> test-amd64-amd64-pair pass
> test-amd64-i386-pair fail
> test-i386-i386-pair fail
> test-amd64-amd64-pv pass
> test-amd64-i386-pv fail
> test-i386-i386-pv fail
> test-amd64-i386-win-vcpus1 fail
> test-amd64-i386-xl-win-vcpus1 fail
> test-amd64-amd64-win fail
> test-amd64-i386-win fail
> test-i386-i386-win fail
> test-amd64-amd64-xl-win fail
> test-i386-i386-xl-win fail
>
>
> ------------------------------------------------------------
> sg-report-flight on woking.cam.xci-test.com
> logs: /home/xc_osstest/logs
> images: /home/xc_osstest/images
>
> Logs, config files, etc. are available at
> http://www.chiark.greenend.org.uk/~xensrcts/logs
>
> Test harness code can be found at
> http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
>
>
> Not pushing.
>
> ------------------------------------------------------------
> commit 78e7a0c14685d544453e85a331aa7f63831c2d3b
> Merge: 2b494f1... 2808026...
> Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> Date: Mon May 16 13:56:10 2011 -0700
>
> Merge branch 'for-2.6.32/bug-fixes' of
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen into xen/next-2.6.32
>
> * 'for-2.6.32/bug-fixes' of
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen:
> xen/blkback: When writting barriers set the sector number to zero...
> xen/apic: Provide an 'apic_xen' to set the override the
> apic->[read|write] for all cases.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-05-23 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 6:11 [linux test] 7244: regressions - FAIL xen.org
2011-05-23 8:08 ` 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=4DDA32110200007800042C55@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.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).