* [libvirt test] 26885: regressions - FAIL
@ 2014-06-02 18:08 xen.org
0 siblings, 0 replies; only message in thread
From: xen.org @ 2014-06-02 18:08 UTC (permalink / raw)
To: xen-devel; +Cc: ian.jackson
flight 26885 libvirt real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/26885/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf 4 xen-build fail REGR. vs. 26664
build-armhf-libvirt 4 libvirt-build fail REGR. vs. 26664
build-armhf-pvops 4 kernel-build fail REGR. vs. 26664
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt 9 guest-start fail never pass
test-armhf-armhf-libvirt 1 xen-build-check(1) blocked n/a
test-amd64-amd64-libvirt 9 guest-start fail never pass
version targeted for testing:
libvirt 359d9941d04c8d025d9a38e0aec1b20a235d39cc
baseline version:
libvirt c7ca02e6e2086d118645b62ca63ed0b24f48ddf8
------------------------------------------------------------
People who touched revisions under test:
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf fail
build-i386 pass
build-amd64-libvirt pass
build-armhf-libvirt fail
build-i386-libvirt pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-armhf-pvops fail
build-i386-pvops pass
test-amd64-amd64-libvirt fail
test-armhf-armhf-libvirt blocked
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
Not pushing.
------------------------------------------------------------
commit 359d9941d04c8d025d9a38e0aec1b20a235d39cc
Author: Daniel Veillard <veillard@redhat.com>
Date: Mon Jun 2 09:53:30 2014 +0800
Bump version to 1.2.6 for new dev cycle
commit 7455be8ea920f6e8335783e30095124ac9c55a35
Author: Daniel Veillard <veillard@redhat.com>
Date: Mon Jun 2 09:52:44 2014 +0800
Forgot spec changelog in 1.2.5 commit
commit e604b59d79421a6d2454c63e8b0b479755db5608
Author: Daniel Veillard <veillard@redhat.com>
Date: Mon Jun 2 09:47:05 2014 +0800
Release of libvirt-1.2.5
* docs/news.html.in: update for release
* po/*.po*: updated ukrainian localization and regenerated
commit ca50df8eec08e2bb5bb64ea82596f0f919ebd98d
Author: Roman Bogorodskiy <bogorodskiy@gmail.com>
Date: Sun May 11 11:25:08 2014 +0400
docs: bhyve driver documentation improvements
- Document 'domxml-to-native' command
- Mention that the nmdm console support needs an appropriate
kernel module loaded
commit 83c41cebd92d04b27a4dcff7a44232ef200f6a65
Author: Laine Stump <laine@laine.org>
Date: Sun Jun 1 05:21:19 2014 +0300
util: fix DST end date in virtimetest timezones
Reported by: Roman Bogorodskiy <bogorodskiy@gmail.com>
Some of the tests for virTimeLocalOffsetFromUTC set an imaginary
timezone that attempts to force dyalight savings time active all the
time by setting a start date of 0/00:00:00 and end date of
366/23:59:59. Since the day is 0-based, 366 really means "day 367"
which will never occur - this was an attempt to eliminate problems
with DST not being active in some cases right around midnight on
January 1. Even though it didn't completely solve the problem, it
didn't seem to cause harm so it was left in the test timezones.
Although Linux glibc doesn't mind having a DST end date of 366,
FreeBSD refuses to use such timezones, so the tests fail. This patch
changes the 366 to 365.
This may or may not cause failure of the remaining DST tests around
midnight Jan 1. If so, we will need to disable those tests at year's
end too.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-06-02 18:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-02 18:08 [libvirt test] 26885: regressions - FAIL xen.org
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).