From: Karunakar P <karunakarp@amiindia.co.in>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: SCT Test failed
Date: Tue, 4 Jul 2017 12:37:46 +0000 [thread overview]
Message-ID: <A885E3F3F1F22B44AF7CC779C062228EAE4C9D3C@VENUS1.in.megatrends.com> (raw)
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
next reply other threads:[~2017-07-04 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 12:37 Karunakar P [this message]
2017-07-05 0:57 ` SCT Test failed Jin, Eric
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-list 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=A885E3F3F1F22B44AF7CC779C062228EAE4C9D3C@VENUS1.in.megatrends.com \
--to=devel@edk2.groups.io \
/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