ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yusaku Sako <>
Subject Re: Ambari build fails possibly due to dirty npm cache
Date Thu, 11 Sep 2014 23:50:52 GMT
I'll take a look.


On Thu, Sep 11, 2014 at 4:34 PM, jun aoki <> wrote:
> Hi ambari team,
> The build have failed a few times due to some npm install error and I have
> submitted a ticket.
> Those are the failed executions due to the following cause
> + npm install -g brunch
> npm WARN optional dep failed, continuing fsevents@0.2.1
> npm ERR! Error: ENOENT, lstat
> '/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/contrib/views/node.js/target/lib/node_modules/brunch/node_modules/pushserve/node_modules/express/node_modules/cookie-signature/index.js'
> npm ERR! If you need help, you may report this *entire* log,
> npm ERR! including the npm and node versions, at:
> npm ERR!     <>
> The resolution could be this
> npm cache clean
> before
>  npm install -g brunch
> I don't have access to configure the job.
> Committers, can you take a look into it?
> --
> -jun

NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

View raw message