From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [Xen-devel] [ovmf test] 141168: trouble: blocked/broken
Date: Tue, 10 Sep 2019 13:27:43 +0000 [thread overview]
Message-ID: <osstest-141168-mainreport@xen.org> (raw)
flight 141168 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141168/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-pvops <job status> broken
build-amd64-xsm <job status> broken
build-i386 <job status> broken
build-i386-pvops <job status> broken
build-i386-xsm <job status> broken
build-amd64 <job status> broken
build-i386 4 host-install(4) broken REGR. vs. 141091
build-amd64-xsm 4 host-install(4) broken REGR. vs. 141091
build-amd64-pvops 4 host-install(4) broken REGR. vs. 141091
build-amd64 4 host-install(4) broken REGR. vs. 141091
build-i386-xsm 4 host-install(4) broken REGR. vs. 141091
build-i386-pvops 4 host-install(4) broken REGR. vs. 141091
Tests which did not succeed, but are not blocking:
build-i386-libvirt 1 build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
build-amd64-libvirt 1 build-check(1) blocked n/a
version targeted for testing:
ovmf f49421a47dca44c3cfc6d09dfa304239538e2648
baseline version:
ovmf 59b754c9f697d9627b0ccccd327d5132f0e1abb0
Last test of basis 141091 2019-09-06 13:39:28 Z 3 days
Failing since 141158 2019-09-09 03:38:57 Z 1 days 3 attempts
Testing same since 141168 2019-09-09 20:38:46 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Fan, ZhijuX <zhijux.fan@intel.com>
Ray Ni <ray.ni@intel.com>
Zhiju.Fan <zhijux.fan@intel.com>
jobs:
build-amd64-xsm broken
build-i386-xsm broken
build-amd64 broken
build-i386 broken
build-amd64-libvirt blocked
build-i386-libvirt blocked
build-amd64-pvops broken
build-i386-pvops broken
test-amd64-amd64-xl-qemuu-ovmf-amd64 blocked
test-amd64-i386-xl-qemuu-ovmf-amd64 blocked
------------------------------------------------------------
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 build-amd64-pvops broken
broken-job build-amd64-xsm broken
broken-job build-i386 broken
broken-job build-i386-pvops broken
broken-job build-i386-xsm broken
broken-job build-amd64 broken
broken-step build-i386 host-install(4)
broken-step build-amd64-xsm host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-amd64 host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-i386-pvops host-install(4)
Not pushing.
------------------------------------------------------------
commit f49421a47dca44c3cfc6d09dfa304239538e2648
Author: Ray Ni <ray.ni@intel.com>
Date: Tue Aug 27 02:14:45 2019 +0800
MdePkg/BluetoothLeConfig.h: Add type EfiBluetoothSmpPeerAddressList
To support auto-connection, EFI_BLUETOOTH_LE_SMP_DATA_TYPE needs to
add a new data type EfiBluetoothSmpPeerAddressList which associates
with a list of Bluetooth per address connected before.
This new data type was added in UEFI spec 2.7b.
Signed-off-by: Ray Ni <ray.ni@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
commit d6f5a5050b942cc0ec08bdc39900b8231957e18c
Author: Fan, ZhijuX <zhijux.fan@intel.com>
Date: Wed Sep 4 17:54:12 2019 +0800
BaseTools:ECC need to handle lower case 'static'
BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=1778
We are going to add keyword (lower case) 'static' for functions and global
variables which are not referenced outside their current C file.
However, the ECC tool only recognizes upper case 'STATIC' at this moment.
This will lead to issue reports for new codes that follow the above coding
style.
This patch is going to handle lower case 'static'
Cc: Liming Gao <liming.gao@intel.com>
Cc: Bob Feng <bob.c.feng@intel.com>
Signed-off-by: Zhiju.Fan <zhijux.fan@intel.com>
Reviewed-by: Bob Feng <bob.c.feng@intel.com>
commit 03ad3d889c64978c31a8ccd70f1862558bdb0a2d
Author: Fan, ZhijuX <zhijux.fan@intel.com>
Date: Fri Sep 6 11:29:54 2019 +0800
BaseTools:Ecc handle another copyright format
BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=2057
Ecc can not handle the copyright format like
(C) Copyright 2015-2016 Hewlett Packard Enterprise Development LP<BR>
This will cause Ecc to report wrong information.
This patch is going to handle this format
Cc: Liming Gao <liming.gao@intel.com>
Cc: Bob Feng <bob.c.feng@intel.com>
Signed-off-by: Zhiju.Fan <zhijux.fan@intel.com>
Reviewed-by: Bob Feng <bob.c.feng@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2019-09-10 13:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=osstest-141168-mainreport@xen.org \
--to=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xenproject.org \
/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).