public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Jin, Eric" <eric.jin@intel.com>
To: Karunakar P <karunakarp@amiindia.co.in>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: SCT Test failed
Date: Wed, 5 Jul 2017 00:57:44 +0000	[thread overview]
Message-ID: <DA72DC7456565B47808A57108259571F6352379D@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <A885E3F3F1F22B44AF7CC779C062228EAE4C9D3C@VENUS1.in.megatrends.com>

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


      reply	other threads:[~2017-07-05  0:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 12:37 SCT Test failed Karunakar P
2017-07-05  0:57 ` Jin, Eric [this message]

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=DA72DC7456565B47808A57108259571F6352379D@SHSMSX103.ccr.corp.intel.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