From: Jim Fehlig <jfehlig@suse.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xensource.com, "xen.org" <Ian.Jackson@eu.citrix.com>
Subject: Re: [libvirt test] 26128: tolerable FAIL - PUSHED
Date: Tue, 06 May 2014 16:24:05 -0600 [thread overview]
Message-ID: <53696105.7080308@suse.com> (raw)
In-Reply-To: <1399364678.3014.7.camel@kazak.uk.xensource.com>
Ian Campbell wrote:
> Hi Jim,
>
> I just wanted to make sure you had seen these. I think I could figure
> out how to arrange for them to be copied to you if you would prefer that
> to filters etc.
>
Hi Ian,
Yes, I have seen your mails regarding the libvirt addition to osstest.
Sorry for not responding earlier with at least "awesome job, great idea"
:-/. And as far as receiving the mails, I can extract them from the
list via a filter, so no need to arrange for alternate delivery.
> This test (with [libvirt test] in the $subject) is testing the latest
> libvirt master against the master version of Xen (i.e. the version which
> has already passed its own staging gate), IOW to catch regressions
> introduced into libvirt upstream. Currently it is only a build test --
> as you can see it fails at guest-start because noone has taught osstest
> how to drive virsh yet (this is on my todo list but I've got some other
> things to to do now that we have a build test).
>
That's great! Although I'm always struggling for free cycles, let me
know if you need some help once you get to this task.
> You might also want to keep an eye on the libvirt jobs in the main xen
> test flights (those with [xen-unstable test] or [xen-X.Y-testing test]
> in the $subject) which is testing a libvirt which has passed this test
> against the staging version Xen (i.e. as part of Xen's staging->master
> push gate). This should catch regressions introduced from the Xen side
> of things.
>
Ok, thanks for letting me know.
Regards,
Jim
> Ian.
>
> On Sat, 2014-05-03 at 20:00 +0100, xen.org wrote:
>
>> flight 26128 libvirt real [real]
>> http://www.chiark.greenend.org.uk/~xensrcts/logs/26128/
>>
>> Failures :-/ but no regressions.
>>
>> Tests which did not succeed, but are not blocking:
>> test-amd64-i386-libvirt 9 guest-start fail never pass
>> test-armhf-armhf-libvirt 9 guest-start fail never pass
>> test-amd64-amd64-libvirt 9 guest-start fail never pass
>>
>> version targeted for testing:
>> libvirt 064f49a0507ad5239c5f5bc954a48c59950b9225
>> baseline version:
>> libvirt 6077be466efcc2d57679e59db8a4b1626ed0757c
>>
>> ------------------------------------------------------------
>> People who touched revisions under test:
>> Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
>> Daniel P. Berrange <berrange@redhat.com>
>> Dwight Engen <dwight.engen@oracle.com>
>> Eric Blake <eblake@redhat.com>
>> Ian Campbell <ian.campbell@citrix.com>
>> Jiri Denemark <jdenemar@redhat.com>
>> Li Zhang <zhlcindy@linux.vnet.ibm.com>
>> Martin Kletzander <mkletzan@redhat.com>
>> Michal Privoznik <mprivozn@redhat.com>
>> Natanael Copa <ncopa@alpinelinux.org>
>> Pavel Hrdina <phrdina@redhat.com>
>> Roman Bogorodskiy <bogorodskiy@gmail.com>
>> Sahid Orentino Ferdjaoui <sahid.ferdjaoui@cloudwatt.com>
>> Stefan Berger <stefanb@linux.vnet.ibm.com>
>> Steven McDonald <steven.mcdonald@anchor.net.au>
>> ------------------------------------------------------------
>>
>> jobs:
>> build-amd64 pass
>> build-armhf pass
>> build-i386 pass
>> build-amd64-libvirt pass
>> build-armhf-libvirt pass
>> build-i386-libvirt pass
>> build-amd64-oldkern pass
>> build-i386-oldkern pass
>> build-amd64-pvops pass
>> build-armhf-pvops pass
>> build-i386-pvops pass
>> test-amd64-amd64-libvirt fail
>> test-armhf-armhf-libvirt fail
>> test-amd64-i386-libvirt fail
>>
>>
>> ------------------------------------------------------------
>> sg-report-flight on osstest.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
>>
>>
>> Pushing revision :
>>
>> + branch=libvirt
>> + revision=064f49a0507ad5239c5f5bc954a48c59950b9225
>> + . cri-lock-repos
>> ++ . cri-common
>> +++ . cri-getconfig
>> +++ umask 002
>> +++ getconfig Repos
>> +++ perl -e '
>> use Osstest;
>> readglobalconfig();
>> print $c{"Repos"} or die $!;
>> '
>> ++ repos=/export/home/osstest/repos
>> ++ repos_lock=/export/home/osstest/repos/lock
>> ++ '[' x '!=' x/export/home/osstest/repos/lock ']'
>> ++ OSSTEST_REPOS_LOCK_LOCKED=/export/home/osstest/repos/lock
>> ++ exec with-lock-ex -w /export/home/osstest/repos/lock ./ap-push libvirt 064f49a0507ad5239c5f5bc954a48c59950b9225
>> + branch=libvirt
>> + revision=064f49a0507ad5239c5f5bc954a48c59950b9225
>> + . cri-lock-repos
>> ++ . cri-common
>> +++ . cri-getconfig
>> +++ umask 002
>> +++ getconfig Repos
>> +++ perl -e '
>> use Osstest;
>> readglobalconfig();
>> print $c{"Repos"} or die $!;
>> '
>> ++ repos=/export/home/osstest/repos
>> ++ repos_lock=/export/home/osstest/repos/lock
>> ++ '[' x/export/home/osstest/repos/lock '!=' x/export/home/osstest/repos/lock ']'
>> + . cri-common
>> ++ . cri-getconfig
>> ++ umask 002
>> + select_xenbranch
>> + case "$branch" in
>> + tree=libvirt
>> + xenbranch=xen-unstable
>> + '[' xlibvirt = xlinux ']'
>> + linuxbranch=
>> + : tested/2.6.39.x
>> + . ap-common
>> ++ : osstest@xenbits.xensource.com
>> ++ : git://xenbits.xen.org/xen.git
>> ++ : osstest@xenbits.xensource.com:/home/xen/git/xen.git
>> ++ : git://xenbits.xen.org/staging/qemu-xen-unstable.git
>> ++ : git://git.kernel.org
>> ++ : git://git.kernel.org/pub/scm/linux/kernel/git
>> ++ : git
>> ++ : git://libvirt.org/libvirt.git
>> ++ : osstest@xenbits.xensource.com:/home/xen/git/libvirt.git
>> ++ : git://xenbits.xen.org/libvirt.git
>> ++ : git
>> ++ : git://git.sv.gnu.org/gnulib.git
>> ++ : git
>> ++ : git://xenbits.xen.org/osstest/linux-firmware.git
>> ++ : osstest@xenbits.xensource.com:/home/osstest/ext/linux-firmware.git
>> ++ : git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
>> ++ : osstest@xenbits.xensource.com:/home/xen/git/linux-pvops.git
>> ++ : git://xenbits.xen.org/linux-pvops.git
>> ++ : tested/linux-3.4
>> ++ : tested/linux-arm-xen
>> ++ '[' xgit://xenbits.xen.org/linux-pvops.git = x ']'
>> ++ '[' x = x ']'
>> ++ : git://xenbits.xen.org/linux-pvops.git
>> ++ : tested/linux-arm-xen
>> ++ : git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
>> ++ : tested/2.6.39.x
>> ++ : daily-cron.libvirt
>> ++ : daily-cron.libvirt
>> ++ : daily-cron.libvirt
>> ++ : daily-cron.libvirt
>> ++ : http://hg.uk.xensource.com/carbon/trunk/linux-2.6.27
>> ++ : git://xenbits.xen.org/staging/qemu-upstream-unstable.git
>> ++ : daily-cron.libvirt
>> + TREE_LINUX=osstest@xenbits.xensource.com:/home/xen/git/linux-pvops.git
>> + TREE_QEMU_UPSTREAM=osstest@xenbits.xensource.com:/home/xen/git/qemu-upstream-unstable.git
>> + TREE_XEN=osstest@xenbits.xensource.com:/home/xen/git/xen.git
>> + TREE_LIBVIRT=osstest@xenbits.xensource.com:/home/xen/git/libvirt.git
>> + info_linux_tree libvirt
>> + case $1 in
>> + return 1
>> + case "$branch" in
>> + cd /export/home/osstest/repos/libvirt
>> + git push osstest@xenbits.xensource.com:/home/xen/git/libvirt.git 064f49a0507ad5239c5f5bc954a48c59950b9225:xen-tested-master
>> To osstest@xenbits.xensource.com:/home/xen/git/libvirt.git
>> 6077be4..064f49a 064f49a0507ad5239c5f5bc954a48c59950b9225 -> xen-tested-master
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
>
next prev parent reply other threads:[~2014-05-06 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 19:00 [libvirt test] 26128: tolerable FAIL - PUSHED xen.org
2014-05-06 8:24 ` Ian Campbell
2014-05-06 22:24 ` Jim Fehlig [this message]
2014-05-07 8:52 ` 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=53696105.7080308@suse.com \
--to=jfehlig@suse.com \
--cc=Ian.Campbell@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.