Your Linux distribution should have a nuget package available (e.g. https://packages.ubuntu.com/hirsute/nuget) but the EDK2 CI is designed to use the copy of nuget installed with the edk2toolext package. -- Rebecca Cran On 6/29/21 9:44 AM, Steven Shi wrote: > > Cran, Thanks. I’m curious whether the .pytool has native Linux > executable binary to run? It looks the edk2 CI framework has more > dependency in Linux than Windows. > > Thanks > > *Steven Shi*** > > *Intel\IAGS\SFP\FIA (Firmware Infrastructure Automation)*** > > ** > > *From:* devel@edk2.groups.io *On Behalf Of > *Rebecca Cran > *Sent:* Tuesday, June 29, 2021 8:13 PM > *To:* devel@edk2.groups.io; Shi, Steven > *Subject:* Re: [edk2-devel] Do the edk2 CI unit tests work in Linux? > > NuGet.exe is a .NET assembly/executable, so on Linux you'll need to > install Mono (https://www.mono-project.com/ > ). > > -- > > Rebecca Cran > > On 6/28/21 7:45 PM, Steven Shi wrote: > > Hello, > > I’m interested in the edk2 CI unit > tests(https://github.com/tianocore/edk2/tree/master/.pytool > ). I tested > it in my local. It works well in Windows but does not work in > Linux. It looks the NuGet in pytool only has windows version > (C:\steven\unit_test_env\Lib\site-packages\edk2toolext\bin\NuGet.exe) > but not support the Linux. Below is my detail test steps. Do the > edk2 CI unit tests work in Linux? > > 1. Windows : > > c:\steven>py -m venv unit_test_env > > c:\steven>cd  c:\steven\edk2 > > c:\steven\edk2>c:\steven\unit_test_env\Scripts\activate.bat > > (unit_test_env) c:\steven\edk2>pip install --upgrade -r > pip-requirements.txt > > (unit_test_env) c:\steven\edk2>stuart_setup -c > .pytool/CISettings.py TOOL_CHAIN_TAG=VS2019 > > (unit_test_env) c:\steven\edk2>stuart_update -c > .pytool/CISettings.py TOOL_CHAIN_TAG=VS2019 > > (unit_test_env) c:\steven\edk2>edksetup.bat > > (unit_test_env) c:\steven\edk2>edksetup.bat Rebuild > > (unit_test_env) c:\steven\edk2>stuart_ci_build -c > .pytool/CISettings.py TOOL_CHAIN_TAG=VS2019 -a X64,IA32 -t DEBUG > --verbose > > … > > PROGRESS - Overall Build Status: Success > > SECTION - Summary > > PROGRESS - Success > > 2. Linux: > > jshi19@ub2-uefi-b01:~/wksp_efi$ python3 -m venv unit_test_env > > jshi19@ub2-uefi-b01:~/wksp_efi$ source unit_test_env/bin/activate > > (unit_test_env) jshi19@ub2-uefi-b01:~/wksp_efi/edk2-2$ pip install > --upgrade -r pip-requirements.txt > > (unit_test_env) jshi19@ub2-uefi-b01:~/wksp_efi/edk2-2$ make -C > BaseTools/ > > (unit_test_env) jshi19@ub2-uefi-b01:~/wksp_efi/edk2-2$ > stuart_setup -c .pytool/CISettings.py TOOL_CHAIN_TAG=GCC5 > > (unit_test_env) jshi19@ub2-uefi-b01:~/wksp_efi/edk2-2$ > stuart_update -c .pytool/CISettings.py TOOL_CHAIN_TAG=GCC5 > > SECTION - Init SDE > > WARNING - Using Pip Tools based BaseTools > > SECTION - Loading Plugins > > SECTION - Start Invocable Tool > > SECTION - Initial update of environment > > UpdatingWARNING - [SDE] Failed to fetch NugetDependecy: > edk2-acpica-iasl@20200717.0.0 > : [Nuget] We failed to > install this version 20200717.0.0 of edk2-acpica-iasl > > WARNING - [SDE] Failed to fetch NugetDependecy: mu_nasm@2.15.05 > : [Nuget] We failed to install this > version 2.15.05 of mu_nasm > > . Done > > SECTION -       Updated/Verified 3 dependencies > > SECTION - Second pass update of environment > > UpdatingWARNING - [SDE] Failed to fetch NugetDependecy: > edk2-acpica-iasl@20200717.0.0 > : [Nuget] We failed to > install this version 20200717.0.0 of edk2-acpica-iasl > > WARNING - [SDE] Failed to fetch NugetDependecy: mu_nasm@2.15.05 > : [Nuget] We failed to install this > version 2.15.05 of mu_nasm > > . Done > > SECTION -       Updated/Verified 3 dependencies > > ERROR - We were unable to successfully update 2 dependencies in > environment > > SECTION - Summary > > ERROR - Error > > Thanks > > *Steven Shi* > > ** > > ** > >