public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@nuviainc.com>
To: devel@edk2.groups.io, steven.shi@intel.com
Subject: Re: [edk2-devel] Do the edk2 CI unit tests work in Linux?
Date: Tue, 29 Jun 2021 10:42:41 -0600	[thread overview]
Message-ID: <18761d7c-2069-93e2-b444-1ada9e0a8966@nuviainc.com> (raw)
In-Reply-To: <DM4PR11MB5549061F57A9DD34BEDD60378C029@DM4PR11MB5549.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 4396 bytes --]

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 <devel@edk2.groups.io> *On Behalf Of 
> *Rebecca Cran
> *Sent:* Tuesday, June 29, 2021 8:13 PM
> *To:* devel@edk2.groups.io; Shi, Steven <steven.shi@intel.com>
> *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/ 
> <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
>     <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
>     <mailto: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
>     <mailto: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
>     <mailto: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
>     <mailto: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*
>
>     **
>
>     **
>
> 

[-- Attachment #2: Type: text/html, Size: 12140 bytes --]

  parent reply	other threads:[~2021-06-29 16:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29  1:45 Do the edk2 CI unit tests work in Linux? Steven Shi
2021-06-29 12:12 ` [edk2-devel] " Rebecca Cran
2021-06-29 15:44   ` Steven Shi
2021-06-29 15:59     ` Bret Barkelew
2021-06-29 16:37       ` Rebecca Cran
2021-06-29 16:42     ` Rebecca Cran [this message]
2021-06-29 17:02       ` [EXTERNAL] " Bret Barkelew
2021-07-02  0:54         ` Steven Shi
2021-07-02  1:03           ` Bret Barkelew
2021-07-02  1:36             ` Steven Shi
2021-07-02  1:53               ` Bret Barkelew
2021-07-02  2:00               ` Rebecca Cran
2021-07-02  2:43                 ` Steven Shi
2021-07-02  7:23                   ` Steven Shi
2021-07-07 18:54                     ` Sean
2021-07-02  2:45                 ` Bret Barkelew
2021-06-29 15:56   ` Bret Barkelew

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=18761d7c-2069-93e2-b444-1ada9e0a8966@nuviainc.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