public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"rebecca@bsdio.com" <rebecca@bsdio.com>,
	Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [EXTERNAL] [edk2-devel] Information about the VMs used to do EDK2 CI?
Date: Sat, 21 Mar 2020 01:46:42 +0000	[thread overview]
Message-ID: <MWHPR21MB07509B8BAE675C7E795551C3EFF20@MWHPR21MB0750.namprd21.prod.outlook.com> (raw)
In-Reply-To: <46ad7e58-edb7-0819-9542-8d6850598292@bsdio.com>

[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]

CI runs on the DevOps pool for ubuntu-latest and windows-latest, respectively…
https://github.com/tianocore/edk2/blob/0c8ea9fe1adbbee230ee0c68f28b68ca2b0534bc/.azurepipelines/Ubuntu-GCC5.yml#L16
https://github.com/tianocore/edk2/blob/0c8ea9fe1adbbee230ee0c68f28b68ca2b0534bc/.azurepipelines/Windows-VS2019.yml#L17

As for OS, it looks like this table is kept up-to-date:
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops#use-a-microsoft-hosted-agent

I *think* they may be assumed to be single-threaded and parallelism is accomplished via “jobs”:
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops#capabilities-and-limitations
(@Sean<mailto:sean.brogan@microsoft.com> may correct me on that)

What details do you need and I’ll try to find them. 😊

- Bret

From: Rebecca Cran via Groups.Io<mailto:rebecca=bsdio.com@groups.io>
Sent: Friday, March 20, 2020 6:33 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: [EXTERNAL] [edk2-devel] Information about the VMs used to do EDK2 CI?

I was wondering if it might be possible to get information about the VMs
used to run EDK2 CI?

For example I noticed the Edk2ToolsBuild.py script doesn't try and build
BaseTools in parallel, causing it to take 45 seconds - whereas it takes
around 10 when run with "make -j4" and 6 with "make -j16". However,
without knowing the specifications of the VMs used, I'm not sure if I
should work on optimizing things like that to run better.


--
Rebecca Cran






[-- Attachment #2: Type: text/html, Size: 4528 bytes --]

  reply	other threads:[~2020-03-21  1:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21  1:33 Information about the VMs used to do EDK2 CI? Rebecca Cran
2020-03-21  1:46 ` Bret Barkelew [this message]
2020-03-21  3:15   ` [EXTERNAL] [edk2-devel] " Rebecca Cran
2020-03-21 16:41   ` [edk2-devel] " Sean
2020-03-21 23:03     ` Rebecca Cran
2020-03-23 12:38       ` Laszlo Ersek
2020-03-28 20:23         ` Sean
2020-03-28 21:41         ` Andrew Fish

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=MWHPR21MB07509B8BAE675C7E795551C3EFF20@MWHPR21MB0750.namprd21.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