* [xen-unstable-smoke test] 102959: trouble: broken/pass
@ 2016-12-05 19:28 osstest service owner
0 siblings, 0 replies; only message in thread
From: osstest service owner @ 2016-12-05 19:28 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 102959 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/102959/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-i386 <none executed> broken
test-amd64-amd64-libvirt <none executed> broken
build-amd64-libvirt <none executed> broken
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl 12 migrate-support-check fail never pass
test-armhf-armhf-xl 13 saverestore-support-check fail never pass
version targeted for testing:
xen 503148ae5a6d22ba9e63517bade5f0f680a8f47b
baseline version:
xen cc50fa3051947e1b72f87f22767886a7904761fe
Last test of basis 102948 2016-12-05 15:01:20 Z 0 days
Testing same since 102959 2016-12-05 18:01:55 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Tim Deegan <tim@xen.org>
jobs:
build-amd64 pass
build-armhf pass
build-amd64-libvirt broken
test-armhf-armhf-xl pass
test-amd64-amd64-xl-qemuu-debianhvm-i386 broken
test-amd64-amd64-libvirt broken
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
broken-job test-amd64-amd64-xl-qemuu-debianhvm-i386 broken
broken-job test-amd64-amd64-libvirt broken
broken-job build-amd64-libvirt broken
Not pushing.
------------------------------------------------------------
commit 503148ae5a6d22ba9e63517bade5f0f680a8f47b
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Wed Nov 2 15:50:23 2016 +0000
x86/emul: Drop the last remaining uses of bool_t
And drop the compatibility typedef from the userspace harness
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
commit a6c406c1f4a17ef30009090a45470f20f75addde
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Fri Dec 2 13:18:38 2016 +0000
x86/hvm: Assert some expectations in hvm_inject_event()
Check that event->error_code is appropriate for the type/vector combination.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
commit c31f3be9b40d5d4703674b35081cfcbabd4ad8bb
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Tue Oct 25 19:41:01 2016 +0100
x86/emul: Debugging improvements to the test harness
Disable stdout buffering, so logging gets out even if the harness crashes.
Add a verbose option (compile time disabled) which dumps all read/write calls
the harness makes
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
commit 750c5f714b80bf467ccd2af86b7f6ff8d6e578b9
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Fri Dec 2 18:23:02 2016 +0000
x86/shadow: Drop stale adjustment in the PAE second-half search
This shouldn't have been present in c/s 29a57c992 "x86/emul: Rework emulator
event injection". It was a leftover from a previous version of the series.
This conditional has no effect on the behaviour following it, as both
X86EMUL_EXCEPTION and X86EMUL_UNHANDLEABLE fall into the same "return back to
guest" path.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Tim Deegan <tim@xen.org>
commit fb06017f807d45f43b86be33311694c6665ac182
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Tue May 24 11:56:58 2016 +0100
x86/pagewalk: Improve print_gw()
print_gw() has no callers, meaning that it only gets used as part of manual
debugging. As such, the FILE/LINE references are of no practical use, and
voluminous in the log. Additionally, the function becoming empty in a
non-debug build is unhelpful. Switch from gdprintk() to gprintk().
Print the entry and mfn for a specific level on the same line. This halves
the number of lines printed overall. There needs to be a small adjustment to
the #ifdef'ary to maintain the proper l3e behaviour for 3-level paging, where
there is no l3mfn to print.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Tim Deegan <tim@xen.org>
commit ceafbe464f905ae33471ac062f3467ca828f0b5b
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Sun Oct 2 17:28:11 2016 +0100
x86/time: Move cpuid_time_leaf() handling into cpuid_hypervisor_leaves()
This reduces the net complexity of CPUID handling by having all adjustments in
at the same place.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
commit 3d3c4c5c2fe70896ce7f93d61d298f62eb14092f
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Thu Sep 1 10:38:27 2016 +0100
xen/x86: Add a helper to calculate family/model/stepping information
And replace the existing opencoded calculations.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
(qemu changes not included)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-12-05 19:28 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-12-05 19:28 [xen-unstable-smoke test] 102959: trouble: broken/pass osstest service owner
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).