From: "Zhang, Shenglei" <shenglei.zhang@intel.com>
To: Sean Brogan <spbrogan@outlook.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
Sean Brogan <sean.brogan@microsoft.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>
Subject: Re: [edk2-devel] Meet failure when running open ci env locally
Date: Mon, 10 Aug 2020 00:57:27 +0000 [thread overview]
Message-ID: <BL0PR11MB35068200C157E80D2DD402AD8C440@BL0PR11MB3506.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BN8PR07MB6962FCBD0254EBC05285AB47C8490@BN8PR07MB6962.namprd07.prod.outlook.com>
Thanks, Sean. That works.
> -----Original Message-----
> From: Sean Brogan <spbrogan@outlook.com>
> Sent: Friday, August 7, 2020 11:35 PM
> To: devel@edk2.groups.io; Zhang, Shenglei <shenglei.zhang@intel.com>;
> Sean Brogan <sean.brogan@microsoft.com>; Bret Barkelew
> <Bret.Barkelew@microsoft.com>
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Gao, Liming
> <liming.gao@intel.com>
> Subject: Re: [edk2-devel] Meet failure when running open ci env locally
>
> Two issues.
>
> 1. The tool is saying that your repository is out of date for
> dependencies and you must run stuart_update to pull the required
> dependencies. To do an update you need to run stuart_update -c
> .pytool/CISettings.py <plus whatever options are you going to use to build>
>
> 2. You have TOOL_CHAIN_TAG=NO-TARGET. NO-TARGET is the target which
> can
> be set by doing -t NO-TARGET.
>
>
> Please look here for details.
> https://github.com/tianocore/edk2/tree/master/.pytool#running-ci
>
> Hope that helps.
> Thanks
> Sean
>
>
>
> On 8/7/2020 1:26 AM, Zhang, Shenglei wrote:
> > ci_build -c .pytool/CISettings.py TOOL_CHAIN_TAG=NO-TARGET
prev parent reply other threads:[~2020-08-10 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 8:26 Meet failure when running open ci env locally Zhang, Shenglei
2020-08-07 15:35 ` [edk2-devel] " Sean
2020-08-10 0:57 ` Zhang, Shenglei [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=BL0PR11MB35068200C157E80D2DD402AD8C440@BL0PR11MB3506.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