public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pandya, Shivanshi" <Shivanshi.Pandya@dell.com>
To: Bret Barkelew <Bret.Barkelew@microsoft.com>,
	Andrew Fish <afish@apple.com>,
	edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [EXTERNAL] [edk2-devel] Build Failed for QEMU35Pkg
Date: Mon, 12 Apr 2021 17:18:50 +0000	[thread overview]
Message-ID: <SA0PR19MB4410E6BF1866D5C33A2AF1B291709@SA0PR19MB4410.namprd19.prod.outlook.com> (raw)
In-Reply-To: <MW4PR21MB19078A1874818C8B46417887EF709@MW4PR21MB1907.namprd21.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 8007 bytes --]

Hey All,

Thank you for your thoughts and responses. I have figured it out.
The branch has been updated with fix which I missed! Got the successful build done.

Thank you,
Shivanshi

From: Bret Barkelew <Bret.Barkelew@microsoft.com>
Sent: Monday, April 12, 2021 11:32 AM
To: Andrew Fish; edk2-devel-groups-io
Cc: Pandya, Shivanshi
Subject: RE: [EXTERNAL] [edk2-devel] Build Failed for QEMU35Pkg


[EXTERNAL EMAIL]
To my knowledge, we do not currently have a required version; the current state is it either works or it doesn't, and if it doesn't it's on you to figure that out from the failures.

I'm not opposed to adding one - if there's interest. I'd have to think about the best place to add it. The idea of making it its own test is interesting. It wouldn't prevent you from getting other test data, but it would let you know you aren't on the ideal version and there may be unpredictable results. Ponder ponder...

- Bret

From: Andrew Fish<mailto:afish@apple.com>
Sent: Monday, April 12, 2021 9:27 AM
To: edk2-devel-groups-io<mailto:devel@edk2.groups.io>; Bret Barkelew<mailto:Bret.Barkelew@microsoft.com>
Cc: Shivanshi.Pandya@dell.com<mailto:Shivanshi.Pandya@dell.com>
Subject: Re: [EXTERNAL] [edk2-devel] Build Failed for QEMU35Pkg



On Apr 9, 2021, at 6:33 PM, Bret Barkelew via groups.io [nam06.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam06.safelinks.protection.outlook.com/?url=http*3A*2F*2Fgroups.io*2F&data=04*7C01*7Cbret.barkelew*40microsoft.com*7C6d96996208ff4e09af9b08d8fdcfe4ff*7C72f988bf86f141af91ab2d7cd011db47*7C1*7C0*7C637538416634242026*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=2Q27KOA7lPRrGvoT9s*2FyZ2A3R4B897iBiDuCj3zH3IU*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUl!!LpKI!xxjXBjBATp_RrW9GGX0Q2FHITnkPCYub9nTNgqQIxO2voERPEHUob4lYnsAoFKeKmSg$> <bret.barkelew=microsoft.com@groups.io<mailto:bret.barkelew=microsoft.com@groups.io>> wrote:

Andrew,
Not a scheme that I would consider a "good" scheme. You can see what we're running CI against (in Mu and EDK, both), by checking for the  "UsePythonVersion" command in the .azurepipelines/pr-gate-steps.yml file.


Bret,

If I understand correctly the CI list is the recommended versions, but not the required versions. Do we have any concept of the required versions? I guess we could put a python assert to enforce min Python version? I guess we could be more aggressive on the required Python version (forces people to install a custom Python version for the edk2 build), or build a CI test that tests the min Python version for the tools...

Sorry mostly thinking out loud....

Thanks,

Andrew Fish


Shivanshi,
I just ran a build on my system with that exact version of Python (3.9.0). Did your build produce a "BUILD_TOOLS_REPORT.json" file? If so, can you send it?
Can you also send the exact command that you're running when you see this issue?

Thanks!

- Bret

From: Andrew Fish<mailto:afish@apple.com>
Sent: Friday, April 9, 2021 4:54 PM
To: edk2-devel-groups-io<mailto:devel@edk2.groups.io>; Bret Barkelew<mailto:Bret.Barkelew@microsoft.com>
Cc: Shivanshi.Pandya@dell.com<mailto:Shivanshi.Pandya@dell.com>
Subject: [EXTERNAL] Re: [edk2-devel] Build Failed for QEMU35Pkg




On Apr 9, 2021, at 1:55 PM, Bret Barkelew via groups.io [nam06.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam06.safelinks.protection.outlook.com/?url=http*3A*2F*2Fgroups.io*2F&data=04*7C01*7Cbret.barkelew*40microsoft.com*7C6d96996208ff4e09af9b08d8fdcfe4ff*7C72f988bf86f141af91ab2d7cd011db47*7C1*7C0*7C637538416634251982*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=TDUsg4PF7O202XD6JQKQbzSIUB5C9d*2BZWknajLWg2j0*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUl!!LpKI!xxjXBjBATp_RrW9GGX0Q2FHITnkPCYub9nTNgqQIxO2voERPEHUob4lYnsAosk7ARDI$> <bret.barkelew=microsoft.com@groups.io<mailto:bret.barkelew=microsoft.com@groups.io>> wrote:

It looks like a Python 3.8.x vs 3.9.x issue.


Do we have a scheme to require a min Python version?

Thanks,

Andrew Fish


It looks as if you're using Mu Q35 as your platform. Can you tell me what branch you're on?

- Bret

From: Pandya, Shivanshi via groups.io<mailto:Shivanshi.Pandya=dell.com@groups.io>
Sent: Friday, April 9, 2021 1:52 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: [EXTERNAL] [edk2-devel] Build Failed for QEMU35Pkg

Hello,

Build failed with following call trace

build.py...
INFO -  : error C0DE: Unknown fatal error when processing [c:\bea\dfci\mu_tiano_platforms\Common\PRM\PrmPkg\Library\DxePrmModuleDiscoveryLib\DxePrmModuleDiscoveryLib.inf [X64, VS2017, DEBUG]]
INFO -
INFO - (Please send email to devel@edk2.groups.io<mailto:devel@edk2.groups.io> for help, attaching following call stack trace!)
INFO -
INFO - (Python 3.9.0 on win32) Traceback (most recent call last):
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\build\build.py", line 2635, in Main
INFO -     MyBuild.Launch()
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\build\build.py", line 2430, in Launch
INFO -     self._MultiThreadBuildPlatform()
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\build\build.py", line 2238, in _MultiThreadBuildPlatform
INFO -     Wa, self.BuildModules = self.PerformAutoGen(BuildTarget,ToolChain)
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\build\build.py", line 2112, in PerformAutoGen
INFO -     CmdListDict = self._GenFfsCmd(Wa.ArchList)
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\build\build.py", line 2009, in _GenFfsCmd
INFO -     GenFfsDict = GenFds.GenFfsMakefile('', GlobalData.gFdfParser, self, ArchList, GlobalData)
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\GenFds\GenFds.py", line 541, in GenFfsMakefile
INFO -     FdObj.GenFd(Flag=True)
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\GenFds\Fd.py", line 131, in GenFd
INFO -     RegionObj.AddToBuffer (FdBuffer, self.BaseAddress, self.BlockSizeList, self.ErasePolarity, GenFdsGlobalVariable.ImageBinDict, self.DefineVarDict, Flag=Flag)
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\GenFds\Region.py", line 134, in AddToBuffer
INFO -     FvObj.AddToBuffer(FvBuffer, FvBaseAddress, BlockSize, BlockNum, ErasePolarity, Flag=Flag)
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\GenFds\Fv.py", line 127, in AddToBuffer
INFO -     FileName = FfsFile.GenFfs(MacroDict, FvParentAddr=BaseAddress, IsMakefile=Flag, FvName=self.UiFvName)
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\GenFds\FfsInfStatement.py", line 518, in GenFfs
INFO -     InputSectList, InputSectAlignments = self.__GenComplexFileSection__(Rule, FvChildAddr, FvParentAddr, IsMakefile=IsMakefile)
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\GenFds\FfsInfStatement.py", line 969, in __GenComplexFileSection__
INFO -     SectList, Align = Sect.GenSection(self.OutputPath, self.ModuleGuid, SecIndex, self.KeyStringList, self, IsMakefile = IsMakefile)
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\GenFds\EfiSection.py", line 218, in GenSection
INFO -     GenFdsGlobalVariable.GenerateSection(OutputFile, [], 'EFI_SECTION_USER_INTERFACE',
INFO -   File "C:\BEA\DFCI\mu_tiano_platforms\MU_BASECORE\BaseTools\Source\Python\GenFds\GenFdsGlobalVariable.py", line 466, in GenerateSection
INFO -     SectionData.fromstring(Ui.encode("utf_16_le"))
INFO - AttributeError: 'array.array' object has no attribute 'fromstring'

Kind Regards,
Shivanshi

<79C90400E51C4EC6A197393CD98D0F7A.png>



<CC6C706EF927441BBD49E964355D5AA6.png>



[-- Attachment #1.2: Type: text/html, Size: 19194 bytes --]

[-- Attachment #2: image002.png --]
[-- Type: image/png, Size: 157 bytes --]

  reply	other threads:[~2021-04-12 17:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 19:10 Build Failed for QEMU35Pkg Pandya, Shivanshi
2021-04-09 20:54 ` [edk2-devel] " Andrew Fish
2021-04-09 20:55 ` Bret Barkelew
2021-04-09 21:59   ` Pandya, Shivanshi
2021-04-09 23:53   ` [edk2-devel] " Andrew Fish
2021-04-10  1:33     ` [EXTERNAL] " Bret Barkelew
2021-04-12 16:27       ` [EXTERNAL] " Andrew Fish
2021-04-12 16:32         ` Bret Barkelew
2021-04-12 17:18           ` Pandya, Shivanshi [this message]
2021-04-12  1:31     ` 回复: " gaoliming

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=SA0PR19MB4410E6BF1866D5C33A2AF1B291709@SA0PR19MB4410.namprd19.prod.outlook.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