public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Min Xu" <min.m.xu@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"sean.brogan@microsoft.com" <sean.brogan@microsoft.com>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: EDK2 CI Broken
Date: Fri, 1 Apr 2022 01:43:02 +0000	[thread overview]
Message-ID: <PH0PR11MB5064DF7E68A6A786AEBA0A56C5E09@PH0PR11MB5064.namprd11.prod.outlook.com> (raw)
In-Reply-To: <PH0PR11MB5064B70544FD5EAE056F4284C5E09@PH0PR11MB5064.namprd11.prod.outlook.com>

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

Hi, Sean
Do you have some suggestion for this CI failure?

From: Xu, Min M <min.m.xu@intel.com>
Sent: Friday, April 1, 2022 9:14 AM
To: Kinney, Michael D <michael.d.kinney@intel.com>; devel@edk2.groups.io
Cc: Yao, Jiewen <jiewen.yao@intel.com>; Xu, Min M <min.m.xu@intel.com>
Subject: EDK2 CI Broken

Hi,
The EDK2 CI seems broken from yesterday. PR failed with the errors at "Update" and "Copy base tools build log".

/opt/hostedtoolcache/Python/3.9.12/x64/bin/stuart_update -c ArmVirtPkg/PlatformCI/PlatformBuild.py TOOL_CHAIN_TAG=GCC5 -t DEBUG -a AARCH64
(node:2764) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:2764) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:2764) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:2764) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:2764) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:2764) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:2764) Warning: Use Cipheriv for counter mode of aes-256-ctr
SECTION - Init SDE
SECTION - Loading Plugins
SECTION - Start Invocable Tool
SECTION - Initial update of environment
Updating... Done
Traceback (most recent call last):
File "/opt/hostedtoolcache/Python/3.9.12/x64/bin/stuart_update", line 8, in <module>
  sys.exit(main())
File "/opt/hostedtoolcache/Python/3.9.12/x64/lib/python3.9/site-packages/edk2toolext/invocables/edk2_update.py", line 101, in main
  Edk2Update().Invoke()
File "/opt/hostedtoolcache/Python/3.9.12/x64/lib/python3.9/site-packages/edk2toolext/base_abstract_invocable.py", line 146, in Invoke
  retcode = self.Go()
File "/opt/hostedtoolcache/Python/3.9.12/x64/lib/python3.9/site-packages/edk2toolext/invocables/edk2_update.py", line 71, in Go
  (build_env_old, shell_env_old, _) = self.PerformUpdate()
File "/opt/hostedtoolcache/Python/3.9.12/x64/lib/python3.9/site-packages/edk2toolext/invocables/edk2_update.py", line 41, in PerformUpdate
  (success, failure) = self_describing_environment.UpdateDependencies(ws_root, scopes, skipped_dirs)
File "/opt/hostedtoolcache/Python/3.9.12/x64/lib/python3.9/site-packages/edk2toolext/environment/self_describing_environment.py", line 364, in UpdateDependencies
  return build_env.update_extdeps(shell_env)
File "/opt/hostedtoolcache/Python/3.9.12/x64/lib/python3.9/site-packages/edk2toolext/environment/self_describing_environment.py", line 277, in update_extdeps
  results = pool_handle.get()


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

  reply	other threads:[~2022-04-01  1:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  1:13 EDK2 CI Broken Min Xu
2022-04-01  1:43 ` Min Xu [this message]
2022-04-01  3:47   ` Michael D Kinney

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=PH0PR11MB5064DF7E68A6A786AEBA0A56C5E09@PH0PR11MB5064.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