From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@nuviainc.com" <rebecca@nuviainc.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>
Subject: Re: [edk2-devel] [Patch v2][edk2-stable202011 3/4] OvmfPkg/PlatformCI/.azurepiplines: Use stable release of QEMU
Date: Wed, 25 Nov 2020 16:20:18 +0000 [thread overview]
Message-ID: <BL0PR11MB32364007B5EBBC655B4E6B24D2FA0@BL0PR11MB3236.namprd11.prod.outlook.com> (raw)
In-Reply-To: <422b3c4f-0918-89f3-6257-ca28ac1c2dd1@nuviainc.com>
Hi Rebecca,
I think the general approach is to verify the latest version of everything
including the CI infrastructure components.
If a failure is detected due to a new component, then we can temporarily
lock in a previous stable version until the issues with the new component
are resolved.
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
> Sent: Wednesday, November 25, 2020 6:58 AM
> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: Sean Brogan <sean.brogan@microsoft.com>; Bret Barkelew <Bret.Barkelew@microsoft.com>; Liming Gao
> <gaoliming@byosoft.com.cn>; Justen, Jordan L <jordan.l.justen@intel.com>; Laszlo Ersek <lersek@redhat.com>; Ard Biesheuvel
> <ard.biesheuvel@arm.com>
> Subject: Re: [edk2-devel] [Patch v2][edk2-stable202011 3/4] OvmfPkg/PlatformCI/.azurepiplines: Use stable release of QEMU
>
> Related, should we use a known version of Ubuntu in testing?
>
> Currently, there are several lines with 'ubuntu-latest' - e.g.:
>
> .azurepipelines/Ubuntu-GCC5.yml:17: vm_image: 'ubuntu-latest'
> .azurepipelines/Ubuntu-PatchCheck.yml:21: vmImage: 'ubuntu-latest'
>
> OvmfPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml:20: vm_image:
> 'ubuntu-latest'
>
>
> I'm not familiar with how Azure works, but could this cause problems
> when they update their Ubuntu latest image to 21.04 etc. and things
> change under us?
>
>
> --
> Rebecca Cran
>
>
> On 11/24/20 10:07 PM, Michael D Kinney wrote:
> > Install the 2020.08.14 release of QEMU for Windows.
> >
> > The QEMU release from 2020.11.20 is installed into the incorrect
> > directory and is causing EDK II CI failures in the run to shell
> > step.
> >
> > Cc: Sean Brogan <sean.brogan@microsoft.com>
> > Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
> > Cc: Liming Gao <gaoliming@byosoft.com.cn>
> > Cc: Jordan Justen <jordan.l.justen@intel.com>
> > Cc: Laszlo Ersek <lersek@redhat.com>
> > Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
> > Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
> > ---
> > OvmfPkg/PlatformCI/.azurepipelines/Windows-VS2019.yml | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/OvmfPkg/PlatformCI/.azurepipelines/Windows-VS2019.yml b/OvmfPkg/PlatformCI/.azurepipelines/Windows-
> VS2019.yml
> > index 02ed233fdb60..dd19fff50066 100644
> > --- a/OvmfPkg/PlatformCI/.azurepipelines/Windows-VS2019.yml
> > +++ b/OvmfPkg/PlatformCI/.azurepipelines/Windows-VS2019.yml
> > @@ -132,7 +132,7 @@ jobs:
> > build_flags: $(Build.Flags)
> > run_flags: $(Run.Flags)
> > extra_install_step:
> > - - powershell: choco install qemu; Write-Host "##vso[task.prependpath]c:\Program Files\qemu"
> > + - powershell: choco install qemu --version=2020.08.14; Write-Host "##vso[task.prependpath]c:\Program
> Files\qemu"
> > displayName: Install QEMU and Set QEMU on path # friendly name displayed in the UI
> > condition: and(gt(variables.pkg_count, 0), succeeded())
> >
>
>
>
>
next prev parent reply other threads:[~2020-11-25 16:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 5:07 [Patch v2][edk2-stable202011 0/4] Address EDK II CI Failures Michael D Kinney
2020-11-25 5:07 ` [Patch v2][edk2-stable202011 1/4] .azurepipelines/templates/pr-gate-steps.yml: Fetch target branch Michael D Kinney
2020-11-25 5:07 ` [Patch v2][edk2-stable202011 2/4] .azurepipelines/templates/platform-build-run-steps.yml: " Michael D Kinney
2020-11-25 5:07 ` [Patch v2][edk2-stable202011 3/4] OvmfPkg/PlatformCI/.azurepiplines: Use stable release of QEMU Michael D Kinney
2020-11-25 8:01 ` [edk2-devel] " Philippe Mathieu-Daudé
2020-11-25 16:23 ` Michael D Kinney
2021-01-08 9:43 ` chocolatey.org instability [was: OvmfPkg/PlatformCI/.azurepiplines: Use stable release of QEMU] Laszlo Ersek
2020-11-25 14:11 ` [Patch v2][edk2-stable202011 3/4] OvmfPkg/PlatformCI/.azurepiplines: Use stable release of QEMU Laszlo Ersek
2020-11-25 14:57 ` [edk2-devel] " Rebecca Cran
2020-11-25 16:20 ` Michael D Kinney [this message]
2020-11-25 19:35 ` Rebecca Cran
2020-12-01 1:55 ` Michael D Kinney
2020-11-25 5:07 ` [Patch v2][edk2-stable202011 4/4] CryptoPkg/Test/UnitTest/Library/BaseCryptLib: Fix MD5 Hash tests Michael D Kinney
2020-11-25 7:31 ` [edk2-devel] " Gao, Zhichao
2020-11-25 16:39 ` Michael D Kinney
2020-11-25 8:27 ` Yao, Jiewen
2020-11-25 5:11 ` [edk2-devel] [Patch v2][edk2-stable202011 0/4] Address EDK II CI Failures Michael D Kinney
2020-11-25 5:31 ` 回复: " gaoliming
2020-11-25 18:16 ` 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=BL0PR11MB32364007B5EBBC655B4E6B24D2FA0@BL0PR11MB3236.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