From: "Rebecca Cran" <rebecca@nuviainc.com>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
Michael Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] generating the test matrix for local CI runs
Date: Thu, 4 Mar 2021 10:45:20 -0700 [thread overview]
Message-ID: <ce1c5a3a-bb75-d6dc-fbe3-30de7531d951@nuviainc.com> (raw)
In-Reply-To: <95b5738d-6af2-15ea-e69d-759b1599b00d@redhat.com>
On 3/4/21 10:04 AM, Laszlo Ersek wrote:
> (Sigh, my address book pulled one over me -- resending to the correct
> list address now. Please ignore the previous posting that you may have
> gotten "in private".)
>
> Hi All,
>
> while I can run specific CI tests locally, using the commands listed at:
>
> https://github.com/tianocore/edk2/tree/master/.pytool
> https://github.com/tianocore/edk2/tree/master/ArmVirtPkg/PlatformCI
> https://github.com/tianocore/edk2/tree/master/OvmfPkg/PlatformCI
>
> I don't know how I can determine and drive the whole "test plan" locally.
>
> When I submit a PR to github, "something" generates (say) 83 test cases.
> How can I run that "something" locally?
>
> Assume I have the following:
> - a Linux builder VM, with up-to-date tools,
> - a Windows builder VM, with up-to-date tools,
> - a topic branch, on top of "master".
>
> How do I generate and run those same 83 tests, locally?
>
> It has happened to me that all my local CI steps succeeded (meaning both
> the Windows and the Linux builder), but github still rejected the PR --
> the reason was that I failed to think of a particular test that github
> would run. Composing 83 "stuart" command lines isn't something I'd like
> to do manually.
FWIW it looks like people have been looking for similar functionality of
testing a pipeline locally, and not found it.
e.g.:
https://github.com/microsoft/azure-pipelines-agent/issues/1764
https://developercommunity.visualstudio.com/t/yaml-how-to-test-yaml-locally-before-commit/1302759
--
Rebecca Cran
next prev parent reply other threads:[~2021-03-04 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 17:04 generating the test matrix for local CI runs Laszlo Ersek
2021-03-04 17:45 ` Rebecca Cran [this message]
2021-03-04 17:56 ` [EXTERNAL] Re: [edk2-devel] " Bret Barkelew
2021-03-04 18:20 ` Bret Barkelew
2021-03-04 18:32 ` Bret Barkelew
2021-03-04 19:07 ` Laszlo Ersek
2021-03-04 18:45 ` 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=ce1c5a3a-bb75-d6dc-fbe3-30de7531d951@nuviainc.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