public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"rebecca@nuviainc.com" <rebecca@nuviainc.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>,
	"Sean Brogan" <sean.brogan@microsoft.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] IA32 CI builds failing at "Add additional i386 packages"
Date: Wed, 28 Apr 2021 20:00:04 +0000	[thread overview]
Message-ID: <CO1PR11MB49291703F973081C38066F40D2409@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <e80c13a6-4a40-9238-a72b-fe8c1b0dcf80@nuviainc.com>

Hi Rebecca,

I saw this on a personal PR for me this morning too.

I am investigating a solution.

Mike

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
> Sent: Wednesday, April 28, 2021 11:42 AM
> To: devel@edk2.groups.io; Bret Barkelew <Bret.Barkelew@microsoft.com>; Sean Brogan <sean.brogan@microsoft.com>
> Subject: [edk2-devel] IA32 CI builds failing at "Add additional i386 packages"
> 
> I submitted a private build PR
> (https://github.com/tianocore/edk2/pull/1608) and it has failed checks
> because the "Add additional i386 packages" step is failing in IA32 builds.
> 
> 
> https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=22532&view=logs&jobId=af1b9c29-0151-521b-1cd5-
> 62de40828ed7&j=94ff8f78-fa10-5da4-511e-45f4b0f2c979&t=52ca6e1b-3afe-5fc0-a333-1408d0ca13a1
> 
> 
> 2021-04-28T18:35:43.5274562Z Building dependency tree...
> 2021-04-28T18:35:43.5296479Z Reading state information...
> 2021-04-28T18:35:43.7201698Z Some packages could not be installed. This
> may mean that you have
> 2021-04-28T18:35:43.7202690Z requested an impossible situation or if you
> are using the unstable
> 2021-04-28T18:35:43.7203955Z distribution that some required packages
> have not yet been created
> 2021-04-28T18:35:43.7204631Z or been moved out of Incoming.
> 2021-04-28T18:35:43.7205329Z The following information may help to
> resolve the situation:
> 2021-04-28T18:35:43.7205746Z
> 2021-04-28T18:35:43.7206318Z The following packages have unmet dependencies:
> 2021-04-28T18:35:43.7911080Z  libc6-dev:i386 : Depends: libc6:i386 (=
> 2.27-3ubuntu1.4) but it is not going to be installed
> 2021-04-28T18:35:43.7926666Z  libx11-dev:i386 : Depends: libx11-6:i386
> (= 2:1.6.4-3ubuntu0.3) but it is not going to be installed
> 2021-04-28T18:35:43.7928178Z                    Depends: libxau-dev:i386
> (>= 1:1.0.0-1) but it is not going to be installed
> 2021-04-28T18:35:43.7929680Z                    Depends:
> libxdmcp-dev:i386 (>= 1:1.0.0-1) but it is not going to be installed
> 2021-04-28T18:35:43.7931052Z                    Depends:
> libxcb1-dev:i386 but it is not going to be installed
> 2021-04-28T18:35:43.7932420Z  libxext-dev:i386 : Depends: libxext6:i386
> (= 2:1.3.3-1) but it is not going to be installed
> 2021-04-28T18:35:43.8330612Z E: Unable to correct problems, you have
> held broken packages.
> 2021-04-28T18:35:43.8358606Z ##[debug]Exit code 100 received from tool
> '/bin/bash'
> 2021-04-28T18:35:43.8362549Z ##[debug]STDIO streams have closed for tool
> '/bin/bash'
> 2021-04-28T18:35:43.8408313Z ##[error]Bash exited with code '100'.
> 2021-04-28T18:35:43.8416968Z ##[debug]Processed: ##vso[task.issue
> type=error;]Bash exited with code '100'.
> 2021-04-28T18:35:43.8417767Z ##[debug]task result: Failed
> 2021-04-28T18:35:43.8419529Z ##[debug]Processed: ##vso[task.complete
> result=Failed;done=true;]
> 2021-04-28T18:35:43.8441820Z ##[section]Finishing: Add additional i386
> packages
> 
> 
> --
> Rebecca Cran
> 
> 
> 
> 


      reply	other threads:[~2021-04-28 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 18:41 IA32 CI builds failing at "Add additional i386 packages" Rebecca Cran
2021-04-28 20:00 ` Michael D Kinney [this message]

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=CO1PR11MB49291703F973081C38066F40D2409@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