|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [ovmf baseline-only test] 68549: all pass
This run is configured for baseline tests only. flight 68549 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68549/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 35a461cb502877670062560e1edd231aeb35f738 baseline version: ovmf 8d127a5a3a23d960644d1bd78891ae7d55b66544 Last test of basis 68544 2017-02-10 12:19:14 Z 1 days Testing same since 68549 2017-02-11 04:46:56 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Liming Gao <liming.gao@xxxxxxxxx> Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Star Zeng <star.zeng@xxxxxxxxx> jobs: build-amd64-xsm pass build-i386-xsm pass build-amd64 pass build-i386 pass build-amd64-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 pass ------------------------------------------------------------ sg-report-flight on osstest.xs.citrite.net logs: /home/osstest/logs images: /home/osstest/images Logs, config files, etc. are available at http://osstest.xs.citrite.net/~osstest/testlogs/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Push not applicable. ------------------------------------------------------------ commit 35a461cb502877670062560e1edd231aeb35f738 Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Date: Wed Jan 25 15:18:13 2017 +0800 MdePkg/Pci22.h: Deprecate out-of-Spec IncompatiblePciDevice macros DEVICE_ID_NOCARE is defined as 0xFFFF but Spec says (UINT64) -1 should be used to match any VendorId/DeviceId/RevisionId/ SubsystemVendorId/SubsystemDeviceId. PCI_BAR_OLD_ALIGN/PCI_BAR_EVEN_ALIGN/PCI_BAR_SQUAD_ALIGN/ PCI_BAR_DQUAD_ALIGN are defined but Spec doesn't have such definitions. PCI_BAR_ALL is defined as 0xFF but Spec says (UINT64)-1 should be used to match all BARs. PCI_ACPI_UNUSED and PCI_BAR_NOCHANGE are defined as 0 which compliant with Spec but the name is too general and causes confusing. IncompatiblePciDeviceSupport could directly use 0. All of the above macros are marked as deprecated. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx> Cc: Jeff Fan <jeff.fan@xxxxxxxxx> commit a419fd0d2934b640fdd2381b2706aded7bdfb5ca Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Date: Mon Feb 6 11:28:29 2017 +0800 OvmfPkg/IncompatiblePci: Do not use deprecated macros Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> commit 29dbdcabf98f6834d61b17e62995a203323fbd40 Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Date: Thu Jan 26 13:59:20 2017 +0800 MdeModulePkg/IncompatiblePci: Use MAX_UINTN to match any IDs When the VendorId/DeviceId/RevisionId/SubsystemVendorId /SubsystemDeviceId is MAX_UINTN, IncompatiblePciDeviceSupport driver doesn't use it to match any IDs. The patch fixes this bug. Since PciBus driver always calls IncompatiblePciDeviceSupport using IDs read from HW, MAX_UINTN is never passed to this driver. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Cc: Jeff Fan <jeff.fan@xxxxxxxxx> Reviewed-by: Feng Tian <feng.tian@xxxxxxxxx> commit c1a247b8a768e1ebda569dbe9ad7ada8bce3db26 Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Date: Wed Jan 25 16:06:49 2017 +0800 MdeModulePkg/IncompatiblePciDevice: Do not use deprecated macros The patch replaces the following macros: DEVICE_ID_NOCARE (0xFF) --> MAX_UINT64 PCI_ACPI_UNUSED (0) --> 0 PCI_BAR_ALL (0xFF) --> MAX_UINT64 PCI_BAR_NOCHANGE (0) --> 0 PCI_BAR_EVEN_ALIGN --> EVEN_ALIGN (local definition) Since the PciBus driver was updated to accept Spec defined values in previous commit, the above replacements don't impact functionality. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Cc: Jeff Fan <jeff.fan@xxxxxxxxx> Reviewed-by: Feng Tian <feng.tian@xxxxxxxxx> commit 8a93fa1efb24022ac7fea1b725944f962ba9d4c9 Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Date: Wed Jan 25 15:55:55 2017 +0800 MdeModulePkg/PciBus: Accept Spec values as BarIndex and Alignment PI spec IncompatiblePciSupport part defines (UINT64)-1 as all BARs and 0 to use existing alignment. PciBus driver didn't accept these values. It treated 0xFF as all BARs and 0xFFFFFFFFFFFFFFFFULL to use existing alignment. The patch changes the code to still accept old values while also accept values defined in PI spec. So that the driver can provide backward compatibility and follow spec. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Cc: Jeff Fan <jeff.fan@xxxxxxxxx> Reviewed-by: Feng Tian <feng.tian@xxxxxxxxx> commit 9b6483237984d9819809eb13119db8fb1026be31 Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Date: Wed Jan 25 15:22:54 2017 +0800 MdeModulePkg/PciSioSerialDxe: Use MAX_UINT8 instead of PCI_BAR_ALL When BarIndex equals to 0xFF, default value 0 is used as the BAR index. Though PCI_BAR_ALL and MAX_UINT8 shares the same value, using PCI_BAR_ALL is like to match any BAR not BAR 0, it's more proper to use MAX_UINT8 here. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Reviewed-by: Feng Tian <feng.tian@xxxxxxxxx> commit 33bed7561f27802b3a24dcf30978a639c73d835f Author: Star Zeng <star.zeng@xxxxxxxxx> Date: Thu Feb 9 17:06:24 2017 +0800 ShellPkg SmbiosView: Correct some outputs for Type 0/3/10 Type 0: Update "EDD Enhanced Disk Driver)..." to "EDD (Enhanced Disk Driver)..." for STR_SMBIOSVIEW_PRINTINFO_EDD_ENHANCED_DRIVER Type 3: Use L" Laptop" instead of L" LapTop" in SystemEnclosureTypeTable to match SMBIOS spec. Type 10: The BIT7 of Device Type is representing the status of device whether it is enabled or disabled. But current code is not considering the BIT7 and will print "Undefined Value" for enabled device. Type 41 has same definition of Device Type, the code is correct and will be applied to Type 10 by this patch. Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Cc: Jaben Carsey <jaben.carsey@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx> Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx> commit d4c109da73db88713d0a3a274923cbe4316705ab Author: Star Zeng <star.zeng@xxxxxxxxx> Date: Wed Jan 18 16:53:33 2017 +0800 ShellPkg SmbiosView: Eliminate trailing " | " in PrintBitsInfo() Current PrintBitsInfo() will always print an additional trailing " | " for the bit flags, for example, Base Board Feature Flags: Hosting board | Replaceable | Th patch is to eliminate trailing " | " in PrintBitsInfo(), then the output will be like below Base Board Feature Flags: Hosting board | Replaceable Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Cc: Jaben Carsey <jaben.carsey@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx> Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx> commit 4b5d69d3020841d624ae7c4bf886002b6dbcc654 Author: Liming Gao <liming.gao@xxxxxxxxx> Date: Thu Feb 9 15:03:18 2017 +0800 MdeModulePkg PiSmmIpl: Update SmmCommunication comments to match code logic Cc: Star Zeng <star.zeng@xxxxxxxxx> Cc: Feng Tian <feng.tian@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Liming Gao <liming.gao@xxxxxxxxx> Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx> Reviewed-by: Feng Tian <feng.tian@xxxxxxxxx> commit b8654f4de38e8d5ce7b943483222fd1bbc8d5ea2 Author: Liming Gao <liming.gao@xxxxxxxxx> Date: Sat Feb 4 14:41:50 2017 +0800 MdeModulePkg PeiCore: Don't cache GUIDED section with AUTH_NOT_TESTED If GUIDED section authentication has EFI_AUTH_STATUS_NOT_TESTED, its matched extraction ppi may not be installed. So, don't cache its data. Cc: Star Zeng <star.zeng@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Liming Gao <liming.gao@xxxxxxxxx> Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx> commit 9f671b475b154c57cc6de4b629b8ad8900fa4e45 Author: Liming Gao <liming.gao@xxxxxxxxx> Date: Sat Feb 4 14:36:40 2017 +0800 MdeModulePkg PeiCore: Reset PeimNeedingDispatch when its security violation When PEIM is security violation, its matched extraction ppi may not be installed. So, its PeimNeedingDispatch will still reset to TRUE. Cc: Star Zeng <star.zeng@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Liming Gao <liming.gao@xxxxxxxxx> Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx> _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |