From: "Bob Feng" <bob.c.feng@intel.com>
To: Sami Mujawar <Sami.Mujawar@arm.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>
Cc: nd <nd@arm.com>
Subject: Re: [edk2-devel] **NOTICE** EDK II CI downloading gcc_arm_linux tools Failing
Date: Thu, 17 Mar 2022 03:39:54 +0000 [thread overview]
Message-ID: <PH7PR11MB586313C08E1719568050FD29C9129@PH7PR11MB5863.namprd11.prod.outlook.com> (raw)
In-Reply-To: <80A13E6E-AD0E-40F5-8D8C-465C1BC51FAA@arm.com>
[-- Attachment #1: Type: text/plain, Size: 2520 bytes --]
Thank you. The CI was recovered.
Thanks,
Bob
From: Sami Mujawar <Sami.Mujawar@arm.com>
Sent: Wednesday, March 16, 2022 1:43 PM
To: devel@edk2.groups.io; Feng, Bob C <bob.c.feng@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>; Sean Brogan <sean.brogan@microsoft.com>
Cc: nd <nd@arm.com>
Subject: Re: [edk2-devel] **NOTICE** EDK II CI downloading gcc_arm_linux tools Failing
Hi Bob,
The gcc_arm_linux tools failure was due to a broken download link for the toolchain. I noticed this issue while trying to merge https://edk2.groups.io/g/devel/message/87538. However, the download link should now be restored as I was able to merge a change yesterday evening.
I am not sure if you would need to retrigger the stalled pull request for the CI to proceed.
If you still find that the gcc_arm_linux tools are failing, please do let me know.
Regards,
Sami Mujawar
From: <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> on behalf of "Bob Feng via groups.io" <bob.c.feng=intel.com@groups.io<mailto:bob.c.feng=intel.com@groups.io>>
Reply to: "devel@edk2.groups.io<mailto:devel@edk2.groups.io>" <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>, "bob.c.feng@intel.com<mailto:bob.c.feng@intel.com>" <bob.c.feng@intel.com<mailto:bob.c.feng@intel.com>>
Date: Wednesday, 16 March 2022 at 01:37
To: "devel@edk2.groups.io<mailto:devel@edk2.groups.io>" <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>, "Kinney, Michael D" <michael.d.kinney@intel.com<mailto:michael.d.kinney@intel.com>>, Sean Brogan <sean.brogan@microsoft.com<mailto:sean.brogan@microsoft.com>>
Subject: Re: [edk2-devel] **NOTICE** EDK II CI downloading gcc_arm_linux tools Failing
Hi Sean,
Do you have anything update for this issue?
Thanks,
Bob
From: Feng, Bob C <bob.c.feng@intel.com<mailto:bob.c.feng@intel.com>>
Sent: Wednesday, March 16, 2022 9:35 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Kinney, Michael D <michael.d.kinney@intel.com<mailto:michael.d.kinney@intel.com>>; Sean Brogan <sean.brogan@microsoft.com<mailto:sean.brogan@microsoft.com>>
Cc: Feng, Bob C <bob.c.feng@intel.com<mailto:bob.c.feng@intel.com>>
Subject: [edk2-devel] **NOTICE** EDK II CI downloading gcc_arm_linux tools Failing
Hello,
The EDK II CI downloading gcc_arm_linux tools failing right now that cause some of the CI build task failed.
First failure occurred on 3-15-2022.
The issue is being worked.
Thank you for your patience.
Best Regards,
Bob Feng
[-- Attachment #2: Type: text/html, Size: 8357 bytes --]
prev parent reply other threads:[~2022-03-17 3:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 1:34 [edk2-devel] **NOTICE** EDK II CI downloading gcc_arm_linux tools Failing Bob Feng
2022-03-16 1:35 ` Bob Feng
2022-03-16 5:42 ` Sami Mujawar
2022-03-17 3:39 ` Bob Feng [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=PH7PR11MB586313C08E1719568050FD29C9129@PH7PR11MB5863.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