public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sean" <spbrogan@outlook.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Leif Lindholm <leif@nuviainc.com>,
	"ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>,
	Sami Mujawar <sami.mujawar@arm.com>,
	Jiewen Yao <jiewen.yao@intel.com>,
	supreeth.venkatesh@arm.com,
	"kun.q@outlook.com" <kun.q@outlook.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>
Subject: CI is failing - June 2021
Date: Fri, 11 Jun 2021 20:41:05 -0700	[thread overview]
Message-ID: <BY3PR19MB4900FE0F599E4256CD65D037C8339@BY3PR19MB4900.namprd19.prod.outlook.com> (raw)

The CI system is failing around the spellcheck plugin.
https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=23772&view=results


The patch never got merged (15 months ago and again 8 months ago) to 
update nodejs to a newer version.  See bug 
https://bugzilla.tianocore.org/show_bug.cgi?id=2618

This has now caused the spell checker to stop working and is then 
causing an error which is breaking the CI builds.
Updating Node resolves this error.

But after updating a few packages fail because of spelling errors. 
ArmPkg, ArmPlatformPkg, and StandaloneMMPkg.

More info being tracked in this
https://bugzilla.tianocore.org/show_bug.cgi?id=3445

Please prioritize reviewing the patch series that will be sent out soon

FYI - There is also another bug that is hiding a few of the spelling 
failures on linux machines.
https://bugzilla.tianocore.org/show_bug.cgi?id=3454



Thanks
Sean





             reply	other threads:[~2021-06-12  3:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12  3:41 Sean [this message]
2021-06-12  3:47 ` [edk2-devel] CI is failing - June 2021 Kun Qin

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=BY3PR19MB4900FE0F599E4256CD65D037C8339@BY3PR19MB4900.namprd19.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