From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xensource.com, "xen.org" <ian.jackson@eu.citrix.com>
Subject: Re: [xen-unstable test] 22184: regressions - trouble: broken/fail/pass
Date: Sat, 30 Nov 2013 11:20:26 +0000 [thread overview]
Message-ID: <1385810426.23632.41.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <5299C445.5070100@citrix.com>
On Sat, 2013-11-30 at 11:56 +0100, Roger Pau Monné wrote:
> On 30/11/13 04:44, xen.org wrote:
> > flight 22184 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 22106
> > test-amd64-i386-xl-win7-amd64 9 guest-localmigrate fail REGR. vs. 22106
> >
> > Regressions which are regarded as allowable (not blocking):
> > test-amd64-i386-freebsd10-i386 3 host-install(3) broken blocked in 22106
> >
> > Tests which did not succeed, but are not blocking:
> > test-amd64-i386-freebsd10-amd64 7 freebsd-install fail never pass
>
> By looking at the logs it seems like if the VG name has '-' on it they
> get replaced to '--' by the device mapper, so the right path should be:
>
> /dev/mapper/lake--frog-freebsd.guest.osstest--disk3
>
> I have a completely untested patch to fix this (I also have to say my
> perl skills are really limited, so probably there's a better way to do
> this):
You can/should probably abstract Osstest::Debian.pm:lvm_lv_name() into a
more common location.
Ian.
next prev parent reply other threads:[~2013-11-30 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 3:44 [xen-unstable test] 22184: regressions - trouble: broken/fail/pass xen.org
2013-11-30 10:56 ` Roger Pau Monné
2013-11-30 11:20 ` Ian Campbell [this message]
2013-12-02 15:22 ` Roger Pau Monné
2013-12-02 15:26 ` Ian Jackson
2013-12-02 9:36 ` Jan Beulich
2013-12-02 10:14 ` Ian Campbell
2013-12-02 11:47 ` Ian Jackson
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=1385810426.23632.41.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@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).