From: "Sean" <sean.brogan@microsoft.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH] .azurepipelines: Enable CI for OvmfPkg and EmulatorPkg
Date: Mon, 30 Mar 2020 10:00:59 -0700 [thread overview]
Message-ID: <19211.1585587659874241589@groups.io> (raw)
In-Reply-To: <CAKv+Gu_kNKbgXcBQTj9hCq0GkpSc5PVxtoCuj=e9OrHPjHa=fg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Mon, Mar 30, 2020 at 02:36 AM, Ard Biesheuvel wrote:
>
> It should be trivial to extend this to ARM, using TCG emulation.
>
> One question though: what happens if the boot does not make it to the
> shell, and crashes for some reason? The QEMU process will hang, so I'd
> assume some kind of timeout should be applied?
It has a 1 minute timeout and then the build will kill the process.
The bootlog is uploaded in all cases so you can then look at the log.
Here is an example where i didn't configure QEMU right: https://dev.azure.com/tianocore/edk2-ci-play/_build/results?buildId=4942&view=logs&j=6fb09fdb-58e7-5b12-0698-873f788bd2e9&t=e63402bd-99b5-5ddd-38f9-868e9402ecc0
And the last lines in the bootlog.txt show
MaxCpuCountInitialization: BootCpuCount=1 mMaxCpuCount=1
Q35BoardVerification: no TSEG (SMRAM) on host bridge DID=0x1237; only DID=0x29C0 (Q35) is supported
ASSERT /home/vsts/work/1/s/OvmfPkg/PlatformPei/Platform.c(564): ((BOOLEAN)(0==1))
[-- Attachment #2: Type: text/html, Size: 1367 bytes --]
next prev parent reply other threads:[~2020-03-30 17:00 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 [this message]
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
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=19211.1585587659874241589@groups.io \
--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