public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: devel@edk2.groups.io, sean.brogan@microsoft.com
Cc: Leif Lindholm <leif@nuviainc.com>
Subject: Re: [edk2-devel] [PATCH] .azurepipelines: Enable CI for OvmfPkg and EmulatorPkg
Date: Mon, 6 Apr 2020 12:11:16 +0200	[thread overview]
Message-ID: <5d642758-d8f1-ef6d-8ca8-229ff496a893@arm.com> (raw)
In-Reply-To: <22879.1586068785483835499@groups.io>

On 4/5/20 8:39 AM, Sean via groups.io wrote:
> Platform and Core CI patches are ready for review.  I have 14 commits here.
> https://github.com/spbrogan/edk2/tree/PlatformAndCoreCIForOvmfArmVirtEmulatorPackages
> 
> This adds support for "Platform CI" for ArmVirtPkg, OvmfPkg, and 
> EmulatorPkg.
> Each readme has live status and links to the builds as well as details 
> of how to build and run the same way the CI server will.
> ArmVirt: 
> https://github.com/spbrogan/edk2/blob/PlatformAndCoreCIForOvmfArmVirtEmulatorPackages/ArmVirtPkg/README-pytools.md
> Emulator: 
> https://github.com/spbrogan/edk2/blob/PlatformAndCoreCIForOvmfArmVirtEmulatorPackages/EmulatorPkg/README-pytools.md
> OvmfPkg: 
> https://github.com/spbrogan/edk2/blob/PlatformAndCoreCIForOvmfArmVirtEmulatorPackages/OvmfPkg/README-pytools.md
> 
> It also adds ArmVirtPkg, OvmfPkg, and EmulatorPkg to Core CI just for 
> the code evaluation tests (not compiling).  Details of those tests are 
> here: 
> https://github.com/spbrogan/edk2/tree/PlatformAndCoreCIForOvmfArmVirtEmulatorPackages/.pytool
> 
> ArmVirtPkg, OvmfPkg, and EmulatorPkg maintainers please review and let 
> me know what the next step for you package is.  This is ready to commit 
> from my perspective and has already caught a few issues in the last 
> couple of weeks.
> 

Thanks Sean. This is all looking really good. I think this stuff is 
ready to be sent to the mailing list for wider review.

> Finally there are a few pending bugs that should get fixed and at least 
> a couple of gaps I have identified. These are not fixed in the above 14 
> commits.
> 
>  1. OvmfPkg
>      1. https://bugzilla.tianocore.org/show_bug.cgi?id=2662 -- Blocking
>         Core CI
>      2. https://bugzilla.tianocore.org/show_bug.cgi?id=2661 -- Blocking
>         Platform CI
>      3. Spell check in audit mode
>  2. EmulatorPkg
>      1. https://bugzilla.tianocore.org/show_bug.cgi?id=2663 -- Ignore
>         added to Core CI
>      2. https://bugzilla.tianocore.org/show_bug.cgi?id=2639 -- Feature
>         in Platform CI turned off
>      3. https://bugzilla.tianocore.org/show_bug.cgi?id=2638 -- Feature
>         in Platform CI turned off
>      4. Spell check in audit mode
>  3. ArmVirtPkg
>      1. No builds on Windows or with VS toolchain -- Feature in Platform
>         CI turned off

Leif has looked into this in the past. As I understand it, it is simply 
a lack of .asm versions of the various assembler source files in ArmLib, 
ArmMmuLib and the startup code in ArmPlatformPkg.



-- 
Ard.

  reply	other threads:[~2020-04-06 10:11 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  7:04 [PATCH] .azurepipelines: Enable CI for OvmfPkg and EmulatorPkg Zhang, Shenglei
2020-03-26  7:11 ` [edk2-devel] " Rebecca Cran
2020-03-26  7:50   ` [EXTERNAL] " Bret Barkelew
2020-03-26  8:43 ` Ard Biesheuvel
2020-03-26  8:45   ` Zhang, Shenglei
2020-03-27 14:36   ` Laszlo Ersek
2020-03-27 14:39     ` Laszlo Ersek
2020-03-26 23:26 ` [EXTERNAL] " Bret Barkelew
2020-03-27  0:00   ` Michael D Kinney
2020-03-27  0:14     ` Bret Barkelew
2020-03-27  1:59       ` Michael D Kinney
2020-03-27  2:04         ` Liming Gao
2020-03-27  2:50           ` Sean
2020-03-28  2:29 ` [edk2-devel] " Sean
2020-03-28  2:38   ` Rebecca Cran
2020-03-28  2:48     ` Sean
2020-03-28 19:29       ` Sean
2020-03-28 20:28         ` Ard Biesheuvel
2020-03-28 21:47           ` Sean
2020-03-29  8:51             ` Ard Biesheuvel
2020-03-29 23:16               ` Sean
2020-03-30  1:44                 ` Andrew Fish
2020-03-30  6:07                 ` Ard Biesheuvel
2020-03-30  9:31                   ` Sean
2020-03-30  9:35                     ` Ard Biesheuvel
2020-03-30 17:00                       ` Sean
2020-03-30 17:04                         ` Ard Biesheuvel
2020-03-30 17:11                           ` Sean
2020-03-30 17:44                             ` Ard Biesheuvel
2020-03-30 19:07                               ` Sean
2020-03-30 19:51                                 ` Ard Biesheuvel
2020-03-30 20:56                               ` Laszlo Ersek
2020-03-30 21:03                                 ` Sean
2020-03-30 21:13                                   ` Rebecca Cran
2020-04-05  6:39                                   ` Sean
2020-04-06 10:11                                     ` Ard Biesheuvel [this message]
2020-04-07 13:21                                       ` Laszlo Ersek
2020-03-30 21:22                                 ` Ard Biesheuvel
2020-03-31 12:13                                   ` Laszlo Ersek
2020-03-30 21:11                   ` Laszlo Ersek
2020-03-30 21:29                     ` Michael D Kinney
2020-03-30 21:42                       ` Sean
2020-03-30 21:46                         ` Ard Biesheuvel
2020-03-31  6:31                           ` Sean
2020-03-31  6:40                             ` Ard Biesheuvel
2020-03-31 16:26                               ` Sean
2020-03-31 16:32                                 ` Ard Biesheuvel
2020-03-30 22:45                         ` Rebecca Cran
2020-03-30 22:58                         ` Michael D Kinney
2020-03-31 12:27                       ` Laszlo Ersek

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=5d642758-d8f1-ef6d-8ca8-229ff496a893@arm.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