* SCT Test failed
@ 2017-07-04 12:37 Karunakar P
2017-07-05 0:57 ` Jin, Eric
0 siblings, 1 reply; 2+ messages in thread
From: Karunakar P @ 2017-07-04 12:37 UTC (permalink / raw)
To: edk2-devel@lists.01.org
Hi All,
SCT GenericTest failed NetworkPkg.
SCT version used:- UEFI2.5A_SCT_II_Release\UEFISCT\SctPackageX64
[Following are the test results]
GenericTest\EFICompliantTest 5.22.1.2.5 0 0 98551AE7-5020-4DDD-861A-CFFFB4D60382 FAIL EFI Compliant - PXE_BC protocols and one of UNDI/SNP/MNP must be implemented if a platform supports to boot from a network device. x:\uefi-sct\SctPkg\TestCase\UEFI\EFI\Generic\EfiCompliant\BlackBoxTest\EfiCompliantBBTestPlatform_uefi.c:1428:SetupMode equal zero - No 0x00010001 A0A8BED3-3D6F-4AD8-907A-84D52EE1543B No device path PlatformSpecificElements_0_0_A0A8BED3-3D6F-4AD8-907A-84D52EE1543B.log
GenericTest\EFICompliantTest 5.22.1.2.23 0 0 CB6F7B77-0B15-43F7-A95B-8C7F9FD70B21 FAIL UEFI-Compliant - EFI_TLS_PROTOCOL, EFI_TLS_SERVICE_BINDING_PROTOCOL, EFI_TLS_CONFIGURATION_PROTOCOL must be existed if the platform supports TLS feature. x:\uefi-sct\SctPkg\TestCase\UEFI\EFI\Generic\EfiCompliant\BlackBoxTest\EfiCompliantBBTestPlatform_uefi.c:3261:TLSSB-Y, TLSConfig-N 0x00010001 A0A8BED3-3D6F-4AD8-907A-84D52EE1543B No device path PlatformSpecificElements_0_0_A0A8BED3-3D6F-4AD8-907A-84D52EE1543B.log
Note: Along with above two failures some other failures also present.
Please let us know the details if fix is already present for this failures.
Please look into it and provide your comments/suggestions.
Thanks,
karunakar
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: SCT Test failed
2017-07-04 12:37 SCT Test failed Karunakar P
@ 2017-07-05 0:57 ` Jin, Eric
0 siblings, 0 replies; 2+ messages in thread
From: Jin, Eric @ 2017-07-05 0:57 UTC (permalink / raw)
To: Karunakar P, edk2-devel@lists.01.org
Hi karunakar,
I forward this discussion to UTWG since the UEFI SCT is not opensource project.
Best Regards
Eric
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Karunakar P
Sent: Tuesday, July 4, 2017 8:38 PM
To: edk2-devel@lists.01.org
Subject: [edk2] SCT Test failed
Hi All,
SCT GenericTest failed NetworkPkg.
SCT version used:- UEFI2.5A_SCT_II_Release\UEFISCT\SctPackageX64
[Following are the test results]
GenericTest\EFICompliantTest 5.22.1.2.5 0 0 98551AE7-5020-4DDD-861A-CFFFB4D60382 FAIL EFI Compliant - PXE_BC protocols and one of UNDI/SNP/MNP must be implemented if a platform supports to boot from a network device. x:\uefi-sct\SctPkg\TestCase\UEFI\EFI\Generic\EfiCompliant\BlackBoxTest\EfiCompliantBBTestPlatform_uefi.c:1428:SetupMode equal zero - No 0x00010001 A0A8BED3-3D6F-4AD8-907A-84D52EE1543B No device path PlatformSpecificElements_0_0_A0A8BED3-3D6F-4AD8-907A-84D52EE1543B.log
GenericTest\EFICompliantTest 5.22.1.2.23 0 0 CB6F7B77-0B15-43F7-A95B-8C7F9FD70B21 FAIL UEFI-Compliant - EFI_TLS_PROTOCOL, EFI_TLS_SERVICE_BINDING_PROTOCOL, EFI_TLS_CONFIGURATION_PROTOCOL must be existed if the platform supports TLS feature. x:\uefi-sct\SctPkg\TestCase\UEFI\EFI\Generic\EfiCompliant\BlackBoxTest\EfiCompliantBBTestPlatform_uefi.c:3261:TLSSB-Y, TLSConfig-N 0x00010001 A0A8BED3-3D6F-4AD8-907A-84D52EE1543B No device path PlatformSpecificElements_0_0_A0A8BED3-3D6F-4AD8-907A-84D52EE1543B.log
Note: Along with above two failures some other failures also present.
Please let us know the details if fix is already present for this failures.
Please look into it and provide your comments/suggestions.
Thanks,
karunakar
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-07-05 0:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-07-04 12:37 SCT Test failed Karunakar P
2017-07-05 0:57 ` Jin, Eric
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox