From: "Zhang, Shenglei" <shenglei.zhang@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Zhang, Shenglei" <shenglei.zhang@intel.com>
Subject: Meet failure when running open ci env locally
Date: Fri, 7 Aug 2020 08:26:14 +0000 [thread overview]
Message-ID: <BL0PR11MB35062A1BF72EE7A2E7F3FB1B8C490@BL0PR11MB3506.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
Hi folks,
I met a failure when I tried running a ci plugin locally. Does anybody know how to deal with it?
Command and build log are listed below.
cmd: stuart_ci_build -c .pytool/CISettings.py TOOL_CHAIN_TAG=NO-TARGET
build log:
SECTION - Init SDE
ERROR - Dependency 'mu_nasm' is not met!
ERROR - Dependency 'iasl' is not met!
Traceback (most recent call last):
File "C:\Python37\lib\runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "C:\Python37\lib\runpy.py", line 85, in _run_code
exec(code, run_globals)
File "C:\code\AllPkg\pytool-ext-venv\Scripts\stuart_ci_build.exe\__main__.py", line 9, in <module>
File "c:\code\allpkg\pytool-ext-venv\lib\site-packages\edk2toolext\invocables\edk2_ci_build.py", line 246, in main
Edk2CiBuild().Invoke()
File "c:\code\allpkg\pytool-ext-venv\lib\site-packages\edk2toolext\base_abstract_invocable.py", line 122, in Invoke
raise RuntimeError("SDE is not current. Please update your env before running this tool.")
RuntimeError: SDE is not current. Please update your env before running this tool.
Thanks,
Shenglei
[-- Attachment #2: Type: text/html, Size: 3979 bytes --]
next reply other threads:[~2020-08-07 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 8:26 Zhang, Shenglei [this message]
2020-08-07 15:35 ` [edk2-devel] Meet failure when running open ci env locally Sean
2020-08-10 0:57 ` Zhang, Shenglei
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=BL0PR11MB35062A1BF72EE7A2E7F3FB1B8C490@BL0PR11MB3506.namprd11.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