ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7271) trunk commit build unstable due to npm installation (?)
Date Tue, 16 Sep 2014 17:56:33 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135830#comment-14135830
] 

Yusaku Sako commented on AMBARI-7271:
-------------------------------------

Update.  We haven't seen this particular problem since Build #249 and a number of builds have
been succeeding on H11.  We are at #261 now.


> trunk commit build unstable due to npm installation (?) 
> --------------------------------------------------------
>
>                 Key: AMBARI-7271
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7271
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: jun aoki
>            Assignee: jun aoki
>
> The build have failed a few times due to some npm install error.
> https://builds.apache.org/job/Ambari-trunk-Commit/209/console
> https://builds.apache.org/job/Ambari-trunk-Commit/220/console
> https://builds.apache.org/job/Ambari-trunk-Commit/223/console
> I observed following errors upon npm install -g brunch
> {code}
> + 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!     <http://github.com/npm/npm/issues>
> {code}
> The resolution could be this
> https://alicoding.com/how-to-fix-error-enoent-lstat-npm-when-trying-to-install-modules/
> {code}
> npm cache clean 
> {code}
> before
> {code}
>  npm install -g brunch
> {code}
> I don't have access to configure the job so I will let the community know how to solve
this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message