public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney via groups.io" <michael.d.kinney=intel.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>,
	"osde@linux.microsoft.com" <osde@linux.microsoft.com>,
	"leif.lindholm@oss.qualcomm.com" <leif.lindholm@oss.qualcomm.com>
Cc: Oliver Smith-Denny <osde@microsoft.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] CI blockage: VS2019 Ia32 EmulatorPkg failure
Date: Wed, 18 Dec 2024 17:54:23 +0000	[thread overview]
Message-ID: <CO1PR11MB492996844AFCCBECEBC38154D2052@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <b8f1b9f8-a724-4b2c-b2fd-93eeb77eb122@linux.microsoft.com>

I can not reproduce locally either.

I installed VS2022 build tools.

The error message is related to the ability to allocate a specific range of virtual memory.

If that fails on CI agent, but not local envs, it could be related to the 
CI agent windows image being used. 

Mike


> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Michael
> Kubacki via groups.io
> Sent: Wednesday, December 18, 2024 8:48 AM
> To: devel@edk2.groups.io; osde@linux.microsoft.com;
> leif.lindholm@oss.qualcomm.com; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Cc: Oliver Smith-Denny <osde@microsoft.com>
> Subject: Re: [edk2-devel] CI blockage: VS2019 Ia32 EmulatorPkg failure
> 
> I'll update the pipeline names later today.
> 
> Thanks,
> Michael
> 
> On 12/18/2024 10:42 AM, Oliver Smith-Denny via groups.io wrote:
> > Hi Leif,
> >
> > On 12/18/2024 3:13 AM, Leif Lindholm via groups.io wrote:
> >> PR CI jobs are currently failing on Ia32 EmulatorPkg RELEASE (passes
> >> on DEBUG) with
> >> ---
> >> ERROR : Could not allocate PeiServicesTablePage @ 13000000
> >> ---
> >> during the "run to shell" test.
> >>
> >> I note that the build step for
> >> PlatformCI_EmulatorPkg_Windows_VS2019_PR now uses VS2022,
> >> presumably as of https://github.com/tianocore/edk2/pull/6501
> >>
> >> Can someone with access to a VS environment help investigate?
> >
> > I tried to repro this locally yesterday, but unfortunately was not
> > getting one. I will try again today.
> >
> >> We should probably also get the CI job names updated to reflect the
> >> toolchain version they're using.
> >
> > Yes, I asked Mike Kinney to update the pipelines (I unfortunately do
> > not have permission to do so, it has to be done by an admin, Mike
> Kinney
> > or Michael Kubacki I believe will do it. The plan is to also change
> the
> > name of the GCC5 pipeline (Gerd requested this) and instead have more
> > generically named pipelines so when they are updated in the future we
> > don't have this name mismatch.
> >
> > Thanks,
> > Oliver
> >
> >
> >
> >
> >
> 
> 
> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120914): https://edk2.groups.io/g/devel/message/120914
Mute This Topic: https://groups.io/mt/110178683/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-12-18 17:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 11:13 [edk2-devel] CI blockage: VS2019 Ia32 EmulatorPkg failure Leif Lindholm via groups.io
2024-12-18 15:42 ` Oliver Smith-Denny via groups.io
2024-12-18 16:48   ` Michael Kubacki via groups.io
2024-12-18 17:54     ` Michael D Kinney via groups.io [this message]
2024-12-18 20:30       ` Michael D Kinney via groups.io
2024-12-18 20:33         ` Michael D Kinney via groups.io
2024-12-18 20:44           ` Michael Kubacki via groups.io
2024-12-18 21:26             ` Michael Kubacki via groups.io
2024-12-18 21:47               ` Michael D Kinney via groups.io
2024-12-18 23:03                 ` Michael D Kinney via groups.io
     [not found] <1812411E4A564231.26783@groups.io>
2024-12-18 14:34 ` Leif Lindholm via groups.io

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=CO1PR11MB492996844AFCCBECEBC38154D2052@CO1PR11MB4929.namprd11.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