From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>
Subject: [PATCH v2 1/5] .azurepipelines: Use Python 3.8
Date: Fri, 1 Apr 2022 21:31:52 -0400 [thread overview]
Message-ID: <20220402013156.2640-2-mikuback@linux.microsoft.com> (raw)
In-Reply-To: <20220402013156.2640-1-mikuback@linux.microsoft.com>
From: Michael Kubacki <michael.kubacki@microsoft.com>
REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3891
Changes the Python version used in pipelines to 3.8.x (3.8.12) to
workaround an issue discovered after 3.9.10 that causes
stuart_update to fail on a web_dependency (e.g. GCC ARM compilers).
The Python version should be updated to latest once that issue is
root caused and a long term fix is in place. This change is
introduced now to unblock overall CI.
Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Reviewed-by: Sean Brogan <sean.brogan@microsoft.com>
---
.azurepipelines/Ubuntu-PatchCheck.yml | 2 +-
.azurepipelines/templates/platform-build-run-steps.yml | 2 +-
.azurepipelines/templates/pr-gate-steps.yml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/.azurepipelines/Ubuntu-PatchCheck.yml b/.azurepipelines/Ubuntu-PatchCheck.yml
index d55c238592ef..1bc28176b6e8 100644
--- a/.azurepipelines/Ubuntu-PatchCheck.yml
+++ b/.azurepipelines/Ubuntu-PatchCheck.yml
@@ -27,7 +27,7 @@ steps:
- task: UsePythonVersion@0
inputs:
- versionSpec: '3.9.x'
+ versionSpec: '3.8.x'
architecture: 'x64'
- script: |
diff --git a/.azurepipelines/templates/platform-build-run-steps.yml b/.azurepipelines/templates/platform-build-run-steps.yml
index 36cdce9bf8fa..97e7faa26682 100644
--- a/.azurepipelines/templates/platform-build-run-steps.yml
+++ b/.azurepipelines/templates/platform-build-run-steps.yml
@@ -42,7 +42,7 @@ steps:
- task: UsePythonVersion@0
inputs:
- versionSpec: "3.9.x"
+ versionSpec: "3.8.x"
architecture: "x64"
- script: pip install -r pip-requirements.txt --upgrade
diff --git a/.azurepipelines/templates/pr-gate-steps.yml b/.azurepipelines/templates/pr-gate-steps.yml
index 6601c247421b..70c19a462194 100644
--- a/.azurepipelines/templates/pr-gate-steps.yml
+++ b/.azurepipelines/templates/pr-gate-steps.yml
@@ -20,7 +20,7 @@ steps:
- task: UsePythonVersion@0
inputs:
- versionSpec: '3.9.x'
+ versionSpec: '3.8.x'
architecture: 'x64'
- script: pip install -r pip-requirements.txt --upgrade
--
2.28.0.windows.1
next prev parent reply other threads:[~2022-04-02 1:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 1:31 [PATCH v2 0/5] Use windows-2019 VM Image Michael Kubacki
2022-04-02 1:31 ` Michael Kubacki [this message]
2022-04-02 1:31 ` [PATCH v2 2/5] .azurepipelines: Use windows-2019 VM image Michael Kubacki
2022-04-02 1:31 ` [PATCH v2 3/5] EmulatorPkg: " Michael Kubacki
2022-04-02 1:31 ` [PATCH v2 4/5] OvmfPkg: " Michael Kubacki
2022-04-02 1:31 ` [PATCH v2 5/5] BaseTools/Bin: Update GCC ARM compiler version Michael Kubacki
2022-04-02 1:36 ` [edk2-devel] [PATCH v2 0/5] Use windows-2019 VM Image Sean
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=20220402013156.2640-2-mikuback@linux.microsoft.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