public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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 02:31:20 -0700	[thread overview]
Message-ID: <19211.1585560680937587377@groups.io> (raw)
In-Reply-To: <CAKv+Gu_pdaCjZn6542aQZqUKiV=TUzQWpLZwxsHb9EwbP9tt+Q@mail.gmail.com>

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

Thanks.  I was missing the "-s" and Andrew you solution worked for the filesystem.

OVMF: Windows builds and Linux builds and boot to shell. IA32, X64 and IA32x64 - https://dev.azure.com/tianocore/edk2-ci-play/_build/results?buildId=4950&view=results
Emulator: Windows and linux builds and boots to shell. https://dev.azure.com/tianocore/edk2-ci-play/_build/results?buildId=4922&view=results https://dev.azure.com/tianocore/edk2-ci-play/_build/results?buildId=4921&view=results

Src: Needs commit cleanup but its all here. https://github.com/spbrogan/edk2/tree/ci-for-ovmf

Still have a few loose ends on Windows pipeline
1. Windows isn't able to find the QEMU i installed so it is failing to run the emulator.

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

  reply	other threads:[~2020-03-30  9:31 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 [this message]
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
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.1585560680937587377@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