From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 134.134.136.31, mailfrom: eric.jin@intel.com) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by groups.io with SMTP; Mon, 29 Apr 2019 19:03:28 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Apr 2019 19:03:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,412,1549958400"; d="scan'208,217";a="341965891" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga005.fm.intel.com with ESMTP; 29 Apr 2019 19:03:27 -0700 Received: from FMSMSX110.amr.corp.intel.com (10.18.116.10) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 29 Apr 2019 19:03:27 -0700 Received: from shsmsx106.ccr.corp.intel.com (10.239.4.159) by fmsmsx110.amr.corp.intel.com (10.18.116.10) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 29 Apr 2019 19:03:26 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.70]) by SHSMSX106.ccr.corp.intel.com ([169.254.10.213]) with mapi id 14.03.0415.000; Tue, 30 Apr 2019 10:03:24 +0800 From: "Eric Jin" To: Supreeth Venkatesh , "devel@edk2.groups.io" , "Jeff Brasen (jbrasen@nvidia.com)" CC: "Jin, Eric" Subject: Re: [edk2-test] Location of tests for vendor/edk2 specific protocols Thread-Topic: [edk2-test] Location of tests for vendor/edk2 specific protocols Thread-Index: AdTv7QSRSyGgoloHR2qzBexAPSYdlQBlVvFSAFi2PdADBEPUAA== Date: Tue, 30 Apr 2019 02:03:24 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Return-Path: eric.jin@intel.com Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_DA72DC7456565B47808A57108259571F637963B9SHSMSX103ccrcor_" --_000_DA72DC7456565B47808A57108259571F637963B9SHSMSX103ccrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Jeff, For the test for non-standard or vendor specific protocols, in my initial = idea, I would like to see them on a separate space and can be built with SC= T infrastructure thru description files and build scripts provided by vendo= r. Anyone can fetch the UEFI SCT or other specific test with his/her purpose/= interest in this way easily. BTW, documents or spec link need be provided f= or user to understand test object and contribute test better. Anyway, it is a good start to record the request in Bugzilla Feature Reque= st for further discussion. Best Regards Eric From: Supreeth Venkatesh Sent: Monday, April 15, 2019 1:25 AM To: devel@edk2.groups.io; Jeff Brasen (jbrasen@nvidia.com) Cc: Jin, Eric Subject: RE: [edk2-test] Location of tests for vendor/edk2 specific protoc= ols + Eric Thanks Jeff for bringing this up. As mentioned during our discussion on this topic briefly @ UEFI Plugfest 2= 019, I definitely like to see these non-standard protocol tests become part= of test suite. However, there has been no proposal yet, though there were proposals relat= ed to SBBR (Arm's Server Base Boot Requirements). Currently, any new platform tests added have to be added to UEFI SCT descr= iption files and build scripts for it to be included as part of test suite. May I request you to create Bugzilla Feature Request @ https://bugzilla.ti= anocore.org/ under "edk-test" product and "UEFI-SCT" component, as well exp= and on how you like this to be implemented? Supreeth From: devel@edk2.groups.io > On Behalf Of Jeff Brasen via Groups.Io Sent: Friday, April 12, 2019 5:53 PM To: devel@edk2.groups.io Subject: [edk2-devel] [edk2-test] Location of tests for vendor/edk2 specif= ic protocols Now that we have the edk2-test repo with the SCT infrastructure, has there= been any thought for where tests that use this for non-standardized protoc= ols should live? My initial thought is along with the protocols in edk2/edk= 2-platforms. For example if you had Silicon/NVIDIA/Include/Procotol/x.h you= would have Silicon/NVIDIA/TestCase/x/ for this. Has there been any thought= s/plans on this? Thanks, Jeff ________________________________ This email message is for the sole use of the intended recipient(s) and ma= y contain confidential information. Any unauthorized review, use, disclosu= re or distribution is prohibited. If you are not the intended recipient, p= lease contact the sender by reply email and destroy all copies of the origi= nal message. ________________________________ IMPORTANT NOTICE: The contents of this email and any attachments are confi= dential and may also be privileged. If you are not the intended recipient, = please notify the sender immediately and do not disclose the contents to an= y other person, use it for any purpose, or store or copy the information in= any medium. Thank you. --_000_DA72DC7456565B47808A57108259571F637963B9SHSMSX103ccrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Jeff,

 

For the test for non-standard or vendor specific pr= otocols, in my initial idea, I would like to see them on a separate space a= nd can be built with SCT infrastructure thru description files and build sc= ripts provided by vendor.

Anyone can fetch the UEFI SCT or other specific tes= t with his/her purpose/interest in this way easily. BTW, documents or spec = link need be provided for user to understand test object and contribute tes= t better.  

 

Anyway, it is a good start to record the request in= Bugzilla Feature Request for further discussion.

 

Best Regards

Eric

 

From: Supreeth Venkatesh <Supreeth.Venkat= esh@arm.com>
Sent: Monday, April 15, 2019 1:25 AM
To: devel@edk2.groups.io; Jeff Brasen (jbrasen@nvidia.com) <jbra= sen@nvidia.com>
Cc: Jin, Eric <eric.jin@intel.com>
Subject: RE: [edk2-test] Location of tests for vendor/edk2 specific= protocols

 

+ Eric

Thanks Jeff for bringing this up.

As mentioned during our discussion on this topic br= iefly @ UEFI Plugfest 2019, I definitely like to see these non-standard pro= tocol tests become part of test suite.

However, there has been no proposal yet, though the= re were proposals related to SBBR (Arm’s Server Base Boot Requirement= s).

 

Currently, any new platform tests added have to be = added to UEFI SCT description files and build scripts for it to be included= as part of test suite.

May I request you to create Bugzilla Feature Reques= t @ https://bugzilla.tianocore.org/ under “edk-test” product a= nd “UEFI-SCT” component, as well expand on how you like this to= be implemented?

 

Supreeth

 

 

&= nbsp;

Now that we have the edk2-test repo with the SCT in= frastructure, has there been any thought for where tests that use this for = non-standardized protocols should live? My initial thought is along with th= e protocols in edk2/edk2-platforms. For example if you had Silicon/NVIDIA/Include/Procotol/x.h you would have= Silicon/NVIDIA/TestCase/x/ for this. Has there been any thoughts/plans on = this?

 

Thanks,
Jeff

 

This email message is for the sole use of the inten= ded recipient(s) and may contain confidential information.  Any unauth= orized review, use, disclosure or distribution is prohibited.  If you = are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.=

IMPORTANT NOTICE: The contents of this email and an= y attachments are confidential and may also be privileged. If you are not t= he intended recipient, please notify the sender immediately and do not disc= lose the contents to any other person, use it for any purpose, or store or copy the information in any medium. T= hank you.

--_000_DA72DC7456565B47808A57108259571F637963B9SHSMSX103ccrcor_--