public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, sean.brogan@microsoft.com,
	"rfc@edk2.groups.io" <rfc@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
Subject: Re: [edk2-devel] [RFC] EDK II Continuous Integration Phase 1
Date: Fri, 30 Aug 2019 15:11:05 +0200	[thread overview]
Message-ID: <993588d5-b755-9d72-ec2b-7eb1ad6b6a7e@redhat.com> (raw)
In-Reply-To: <DM5PR21MB08425D166A0D03CAADA3FCD9E1BD0@DM5PR21MB0842.namprd21.prod.outlook.com>

Hi Sean,

On 08/30/19 04:21, Sean via Groups.Io wrote:
> would like to see these two efforts merged together.

> Currently if the full set of tests are run we take about 20 minutes.
> This is because compiling MdeModulePkg for debug, release, and host
> based tests take a while.  Most other packages are in the 10 minute
> range.  We do have easy ways to disable or limit certain tests as well
> as expand the matrix to leverage more cloud resources (more parallel
> builds).

> ### Module Inclusion Test - DscCompleteCheck
> ### Code Compilation Test - CompilerPlugin
> ### Host-Based UnitTests - HostUnitTestCompilerPlugin and
>     HostUnitTestDscCompleteCheck
> ### GUID Uniqueness Test - GuidCheck
> ### Cross-Package Dependency Test - DependencyCheck
> ### Library Declaration Test - LibraryClassCheck
> ### Invalid Character Test - CharEncodingCheck

These tests sound awesome!

> ## Next Steps
>
> * Receive community feedback on RFC.
> * Determine where this phase makes sense given existing RFCs from
>   other TianoCore contributors.
> * Optimize testing beharior.
>   * Only run a subset of tests on PRs or individual commits.
>   * Run full testing either once per day or once every several
      commits.

I'd like to keep the per-PR tests down to 10 minutes.

On the other hand, it would be great if all of these tests could be
performed daily or weekly.

Are these tests easy to integrate with the infrastructure described by
Mike?

Thanks,
Laszlo

  reply	other threads:[~2019-08-30 13:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 20:22 [RFC] EDK II Continuous Integration Phase 1 Michael D Kinney
2019-08-29 20:39 ` [edk2-devel] " Michael Zimmermann
2019-08-29 21:08   ` Michael D Kinney
2019-08-30  2:21 ` Sean
2019-08-30 13:11   ` Laszlo Ersek [this message]
2019-09-13 21:00     ` [edk2-devel] " Sean
2019-09-16 11:06       ` Laszlo Ersek
2019-09-19 21:45   ` Michael D Kinney
2019-09-19 21:55   ` Michael D Kinney
2019-09-20 21:29     ` Sean
2019-09-23 17:44       ` Michael D Kinney
2019-09-24 14:05         ` Liming Gao
2019-08-30  8:43 ` Liming Gao
2019-08-30 12:58   ` [edk2-devel] " Laszlo Ersek
2019-09-03  3:39     ` [edk2-rfc] " Ni, Ray
2019-09-03 13:19       ` Laszlo Ersek
2019-09-03 16:41         ` Ni, Ray
2019-09-03 16:55           ` Laszlo Ersek
2019-09-03 17:09             ` Sean
2019-09-03 17:45               ` Laszlo Ersek
2019-09-19 21:13                 ` Michael D Kinney
2019-09-04 23:56           ` rebecca
2019-09-19 17:53   ` Michael D Kinney
2019-08-31 20:31 ` [edk2-rfc] " rebecca
2019-09-17  3:46 ` [edk2-devel] " rebecca

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=993588d5-b755-9d72-ec2b-7eb1ad6b6a7e@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