From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] EDK II CI issues installing choco dependencies - RESOLVED
Date: Sun, 10 Mar 2024 23:33:12 -0700 [thread overview]
Message-ID: <CO1PR11MB492959328E03658511728542D2242@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO1PR11MB49295D7E368B9AE01F63BBE9D2252@CO1PR11MB4929.namprd11.prod.outlook.com>
This issue appears to be resolved
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Michael
> D Kinney
> Sent: Sunday, March 10, 2024 12:16 PM
> To: devel@edk2.groups.io
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: [edk2-devel] EDK II CI issues installing choco dependencies
>
> I am seeing some EDK II CI failures installing choco
> dependencies on windows CI agents.
>
> Here is an example:
>
> https://github.com/tianocore/edk2/pull/5454
> https://dev.azure.com/tianocore/edk2-
> ci/_build/results?buildId=120411&view=logs&j=d32104f1-f467-5bda-fd84-
> d1a8627a9794&t=da01f8aa-41f1-5e7f-f8f1-aaec629da65f&l=85
>
> I see a similar description here that was opened yesterday and
> closed as a choco issue
>
> https://github.com/actions/runner-images/issues/9476
>
> Let me know if anyone notices any resolutions/workarounds.
>
> Mike
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116576): https://edk2.groups.io/g/devel/message/116576
Mute This Topic: https://groups.io/mt/104858552/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2024-03-11 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 19:16 [edk2-devel] EDK II CI issues installing choco dependencies Michael D Kinney
2024-03-11 6:33 ` 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=CO1PR11MB492959328E03658511728542D2242@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