public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Getnat Ejigu" <getnatejigu@gmail.com>
To: Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	 Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [EXTERNAL] [PATCH v1 1/1] UnitTestFrameworkPkg: Sample unit test hangs when running in OVMF/QEMU
Date: Fri, 30 Apr 2021 12:12:18 -0400	[thread overview]
Message-ID: <CAMWsphCaO6qhA0LBPPxOYVWHVm3-NaPZ=N5ePg2_NGEnDZNJWA@mail.gmail.com> (raw)
In-Reply-To: <MW4PR21MB19071624635CE31EC2F48C35EF5E9@MW4PR21MB1907.namprd21.prod.outlook.com>

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

Okay, will do.

Thanks,
-Getnat

On Thu, Apr 29, 2021 at 11:33 PM Bret Barkelew <Bret.Barkelew@microsoft.com>
wrote:

> This change should also be made in:
>
>
> UnitTestFrameworkPkg\Library\UnitTestResultReportLib\UnitTestResultReportLibDebugLib.c
>
> UnitTestFrameworkPkg\Library\UnitTestResultReportLib\UnitTestResultReportLib.c
> (for the prototype)
>
>
>
> - Bret
>
>
>
> *From: *Getnat Ejigu <getnatejigu@gmail.com>
> *Sent: *Thursday, April 29, 2021 10:43 AM
> *To: *devel@edk2.groups.io
> *Cc: *Kinney, Michael D <michael.d.kinney@intel.com>; Sean Brogan
> <sean.brogan@microsoft.com>; Bret Barkelew <Bret.Barkelew@microsoft.com>
> *Subject: *[EXTERNAL] [PATCH v1 1/1] UnitTestFrameworkPkg: Sample unit
> test hangs when running in OVMF/QEMU
>
>
>
> Sample unit tests in UnitTestFrameworkPkg hangs when running in OVMF/QEMU
> environment. Build target is X64/GCC5. Fixing this issue by adding EFIAPI
> to ReportPrint() function that use VA_ARGS.
>
> Signed-off-by: Getnat Ejigu <getnatejigu@gmail.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
> ---
>  UnitTestFrameworkPkg/Library/UnitTestResultReportLib/UnitTestResultReportLibConOut.c
> | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git
> a/UnitTestFrameworkPkg/Library/UnitTestResultReportLib/UnitTestResultReportLibConOut.c
> b/UnitTestFrameworkPkg/Library/UnitTestResultReportLib/UnitTestResultReportLibConOut.c
> index cfb0c5972bd1..db5402d6a210 100644
> ---
> a/UnitTestFrameworkPkg/Library/UnitTestResultReportLib/UnitTestResultReportLibConOut.c
> +++
> b/UnitTestFrameworkPkg/Library/UnitTestResultReportLib/UnitTestResultReportLibConOut.c
> @@ -12,6 +12,7 @@
>  #include <Library/DebugLib.h>
>
>
>
>  VOID
>
> +EFIAPI
>
>  ReportPrint (
>
>    IN CONST CHAR8  *Format,
>
>    ...
>
> --
> 2.25.1
>
>
>

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

  reply	other threads:[~2021-04-30 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 17:43 [PATCH v1 0/1] Sample unit test hangs when running in OVMF/QEMU getnatejigu
2021-04-29 17:43 ` [PATCH v1 1/1] UnitTestFrameworkPkg: " Getnat Ejigu
2021-04-30  3:33   ` [EXTERNAL] " Bret Barkelew
2021-04-30 16:12     ` Getnat Ejigu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-30 21:07 [PATCH v1 0/1] Fix sample unit test hang issue " Getnat Ejigu
2021-04-30 21:07 ` [PATCH v1 1/1] UnitTestFrameworkPkg: Sample unit test hangs when running " Getnat Ejigu
2021-04-30 21:15   ` [EXTERNAL] " Bret Barkelew

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='CAMWsphCaO6qhA0LBPPxOYVWHVm3-NaPZ=N5ePg2_NGEnDZNJWA@mail.gmail.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