public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Sean Brogan <spbrogan@outlook.com>,
	devel@edk2.groups.io, bob.c.feng@intel.com,
	Michael Kinney <michael.d.kinney@intel.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
	Andrew Fish <afish@apple.com>, Ray Ni <ray.ni@intel.com>
Subject: Re: [edk2-devel] [Patch 1/1] EmulatorPkg/PlatformCI: stick with "ubuntu-18.04" for now
Date: Fri, 8 Jan 2021 19:21:38 +0100	[thread overview]
Message-ID: <e5a763d3-85cc-3f4d-e1fe-c72bad5938f8@redhat.com> (raw)
In-Reply-To: <DM6PR07MB718017C8F3C200334B00E28EC8AE0@DM6PR07MB7180.namprd07.prod.outlook.com>

On 01/08/21 19:01, Sean Brogan wrote:
> Looks like the switch to Ubuntu 20.04 was pretty negatively impactful.
> Thanks Laszlo for tracking this down.
> 
> Question to the community (especially those using a Linux environment)
> is what priority should it be to go resolve these and update CI to run
> on Ubuntu 20.04?  General premise is we should stay current without
> being bleeding edge but I want to understand other perspectives.

Yes, we should stay current.

We discussed the topic this Tuesday, on the stewards' meeting.
Subsequently -- two days ago --, I filed the following ticket (and CC'd
you and Bret on it):

  https://bugzilla.tianocore.org/show_bug.cgi?id=3156

It's basically a request to track down & compensate for the specifics of
the Ubuntu 20.04 breakage, and then advance to "ubuntu-latest" again.

Mike's advice was to ask you guys to work out the issues with the Ubuntu
image, interactively; mainly because (if I understood correctly) the
Azure environment may layer additional smarts onto the VM image that's
offered by <https://github.com/actions/virtual-environments>.

Also, as I said in the BZ, I'm not an Ubuntu user, so interactively
tweaking an Ubuntu installation (VM image or otherwise), to make the CI
tasks happy, is not my cup of tea. (Fedora would be different -- but
such an image is not available yet:
<https://github.com/actions/virtual-environments/issues/2307>.)

Mike, please correct any mistakes in the above.

Thanks
Laszlo


> On 12/21/2020 6:53 AM, Laszlo Ersek wrote:
>> On 12/21/20 04:19, Bob Feng wrote:
>>> "vm_image: 'ubuntu-latest'" now refers to Ubuntu Focal (20.04LTS), not
>>> Ubuntu Bionic (18.04LTS), according to
>>> <https://github.com/actions/virtual-environments/issues/1816>.
>>>
>>> In Focal, the "qemu" package is a dummy package with no dependencies,
>>> and
>>> so the actual emulators are not pulled in. Compare:
>>>
>>>    https://packages.ubuntu.com/bionic/qemu
>>>    https://packages.ubuntu.com/focal/qemu
>>>
>>> This causes CI runs to fail.
>>>
>>> It would be best to switch to the "qemu-system" package name, which
>>> continues to depend on the emulators:
>>>
>>>    https://packages.ubuntu.com/bionic/qemu-system
>>>    https://packages.ubuntu.com/focal/qemu-system
>>>
>>> However, while that package does make the emulators available, the
>>> emulators crash. So for now, stick with the previous Ubuntu environment,
>>> which continues to be supported, per
>>> <https://github.com/actions/virtual-environments/issues/1816>.
>>>
>>> Signed-off-by: Bob Feng <bob.c.feng@intel.com>
>>> Cc: Jordan Justen <jordan.l.justen@intel.com>
>>> Cc: Andrew Fish <afish@apple.com>
>>> Cc: Ray Ni <ray.ni@intel.com>
>>> ---
>>>   EmulatorPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/EmulatorPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml
>>> b/EmulatorPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml
>>> index 0e5f4d9961e3..17d62bb69ec5 100644
>>> --- a/EmulatorPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml
>>> +++ b/EmulatorPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml
>>> @@ -15,11 +15,11 @@ pr:
>>>     - master
>>>   jobs:
>>>     - job: Platform_CI
>>>       variables:
>>>         package: 'EmulatorPkg'
>>> -      vm_image: 'ubuntu-latest'
>>> +      vm_image: 'ubuntu-18.04'
>>>         should_run: false
>>>         run_flags: "MAKE_STARTUP_NSH=TRUE"
>>>         #Use matrix to speed up the build process
>>>       strategy:
>>>
>>
>> Merged as commit 3ce3274a5ea4, via
>> <https://github.com/tianocore/edk2/pull/1255>.
>>
>> Thanks,
>> Laszlo
>>
>>
>>
>> 
>>
>>
> 


      parent reply	other threads:[~2021-01-08 18:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21  3:19 [Patch 1/1] EmulatorPkg/PlatformCI: stick with "ubuntu-18.04" for now Bob Feng
2020-12-21 13:47 ` [edk2-devel] " Laszlo Ersek
2020-12-21 14:05   ` Laszlo Ersek
2020-12-21 14:53 ` Laszlo Ersek
2020-12-22  0:04   ` Bob Feng
2021-01-08 18:01   ` Sean
2021-01-08 18:14     ` Rebecca Cran
2021-01-08 18:34       ` Laszlo Ersek
2021-01-08 18:54         ` Rebecca Cran
     [not found]         ` <1658569DBC96D253.25961@groups.io>
2021-01-08 20:20           ` Rebecca Cran
2021-01-11  8:24             ` Laszlo Ersek
2021-01-08 18:21     ` Laszlo Ersek [this message]

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=e5a763d3-85cc-3f4d-e1fe-c72bad5938f8@redhat.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