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; Wed, 12 Jun 2019 02:18:48 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jun 2019 02:18:46 -0700 X-ExtLoop1: 1 Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga001.fm.intel.com with ESMTP; 12 Jun 2019 02:18:47 -0700 Received: from shsmsx107.ccr.corp.intel.com (10.239.4.96) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 12 Jun 2019 02:18:46 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.83]) by SHSMSX107.ccr.corp.intel.com ([169.254.9.98]) with mapi id 14.03.0415.000; Wed, 12 Jun 2019 17:18:45 +0800 From: "Eric Jin" To: Ashish Singhal , Supreeth Venkatesh , "devel@edk2.groups.io" CC: "Jin, Eric" Subject: Re: UEFI SCT Build Broken Thread-Topic: UEFI SCT Build Broken Thread-Index: AQHVIJPlfMT1cuVNJEigMBbSdzwhuKaXvNMw Date: Wed, 12 Jun 2019 09:18:44 +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_DA72DC7456565B47808A57108259571F637C08B1SHSMSX103ccrcor_" --_000_DA72DC7456565B47808A57108259571F637C08B1SHSMSX103ccrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Ashish, Thank for raising this issue. UEFI SCT build pass with edk2-stable201903, and fail on edk2-stable201905, = because edk2 drop the IPF support (4e1daa60f5372c22a11503961061ffa569eaf873= ). UEFI SCT can remove IPF support too. I can follow it tomorrow. Thanks. Best Regards Eric From: Ashish Singhal Sent: Wednesday, June 12, 2019 4:26 AM To: Supreeth Venkatesh ; Jin, Eric ; devel@edk2.groups.io Subject: Re: UEFI SCT Build Broken Supreeth, It is broken against both edk2 tip as well as latest edk2 tag edk2-stable20= 1903. I have filed a bugzilla bug for the same. Thanks Ashish ________________________________ From: Supreeth Venkatesh > Sent: Tuesday, June 11, 2019 1:36 PM To: Ashish Singhal; Eric Jin; devel@edk2.groups.io Subject: RE: UEFI SCT Build Broken Ashish, We are working towards fixing the issue for the next SCT tag corresponding = to edk2 tag. Can you please let us know whether you are referring to edk2 tip or which e= dk2 tag (edk2-stable201903)? If possible, could you log a bug entry in bugzillafor edk2-test/SCT compone= nt? Thanks, Supreeth From: Ashish Singhal > Sent: Tuesday, June 11, 2019 12:18 PM To: Supreeth Venkatesh >; Eric Jin >; deve= l@edk2.groups.io Subject: UEFI SCT Build Broken Hello Eric/Supreeth, With the latest edk2 tag, UEFI SCT tip build is broken. Seems like it needs= Guid/SalSystemTable.h header file which is not in edk2 tree any more. Is a= fix for this already being looked at? Thanks Ashish ________________________________ This email message is for the sole use of the intended recipient(s) and may= contain confidential information. Any unauthorized review, use, disclosur= e or distribution is prohibited. If you are not the intended recipient, pl= ease contact the sender by reply email and destroy all copies of the origin= al message. ________________________________ IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease notify the sender immediately and do not disclose the contents to any= other person, use it for any purpose, or store or copy the information in = any medium. Thank you. --_000_DA72DC7456565B47808A57108259571F637C08B1SHSMSX103ccrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Ashish,

 

Thank for raising this issue.

UEFI SCT build pass with edk2-stable201903, and fail on edk2-stable201905, because edk2 drop the IPF= support (4e1da= a60f5372c22a11503961061ffa569eaf873).

UEFI = SCT can remove IPF support too. I can follow it tomorrow. Thanks.

 

 

Best Regards

Eric

 

From: Ashish Singhal <ashishsingha@nvidia.= com>
Sent: Wednesday, June 12, 2019 4:26 AM
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>; Jin, Eric= <eric.jin@intel.com>; devel@edk2.groups.io
Subject: Re: UEFI SCT Build Broken

 

Supreet= h,

&n= bsp;

It is b= roken against both edk2 tip as well as latest edk2 tag edk2-stable201903.

&n= bsp;

I have = filed a bugzilla bug for the same.

&n= bsp;

Thanks<= o:p>

Ashish<= o:p>

From: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>
Sent: Tuesday, June 11, 2019 1:36 PM
To: Ashish Singhal; Eric Jin; devel@edk2.groups.io
Subject: RE: UEFI SCT Build Broken

 

Ashish,

 

We are working towards fixing the issue for the nex= t SCT tag corresponding to edk2 tag.

Can you please let us know whether you are referrin= g to edk2 tip or which edk2 tag (edk2-stable201903)?

 

If possible, could you log a bug entry in bugzillaf= or edk2-test/SCT component?

 

Thanks,

Supreeth

 

From: Ashish Singhal <ashishsingha@nvidia.com>
Sent: Tuesday, June 11, 2019 12:18 PM
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>; Eric Jin <eric.jin@intel.com>; devel@edk2.groups.io
Subject: UEFI SCT Build Broken

 

Hello = Eric/Supreeth,

 =

With t= he latest edk2 tag, UEFI SCT tip build is broken. Seems like it needs = Guid/SalSystemTable.h header file which is not in edk2 tree any more. Is a = fix for this already being looked at?

 =

Thanks=

Ashish=

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 any= attachments are confidential and may also be privileged. If you are not th= e intended recipient, please notify the sender immediately and do not discl= ose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Th= ank you.

--_000_DA72DC7456565B47808A57108259571F637C08B1SHSMSX103ccrcor_--