From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Gao, Liming" <gaoliming@byosoft.com.cn>,
"michael.kubacki@outlook.com" <michael.kubacki@outlook.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Kubacki, Michael" <michael.kubacki@microsoft.com>,
'Michael Kubacki' <mikuback@linux.microsoft.com>
Subject: Re: [edk2-devel] Open CI failure on CodeQL / Analyze
Date: Fri, 11 Nov 2022 01:40:15 +0000 [thread overview]
Message-ID: <CO1PR11MB4929FAEAD8E396919EAB78EED2009@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <00f201d8f56c$5a439040$0ecab0c0$@byosoft.com.cn>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
The CodeQL GitHub Action: https://github.com/tianocore/edk2/blob/master/.github/workflows/codeql-analysis.yml
Uses Windows-2019 image:
https://github.com/actions/runner-images/blob/main/images/win/Windows2019-Readme.md
That image include Python 3.7.9.
The latest version of Pytools required Python 3.9 or higher.
The CodeQL GitHub Action YML file needs to be updated to install Python 3.9.x.
Mike
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of gaoliming via groups.io
Sent: Thursday, November 10, 2022 5:25 PM
To: michael.kubacki@outlook.com
Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Kubacki, Michael <michael.kubacki@microsoft.com>; 'Michael Kubacki' <mikuback@linux.microsoft.com>; devel@edk2.groups.io
Subject: [edk2-devel] Open CI failure on CodeQL / Analyze
Michael:
Can you help check this failure in open CI? The failure is in https://github.com/tianocore/edk2/pull/3611
Thanks
Liming
[-- Attachment #2: Type: text/html, Size: 43405 bytes --]
next prev parent reply other threads:[~2022-11-11 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 1:24 Open CI failure on CodeQL / Analyze gaoliming
2022-11-11 1:39 ` [edk2-devel] " Michael Kubacki
2022-11-11 1:40 ` Michael D Kinney [this message]
2022-11-11 1:46 ` Michael D Kinney
2022-11-11 1:52 ` Michael Kubacki
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=CO1PR11MB4929FAEAD8E396919EAB78EED2009@CO1PR11MB4929.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