[
https://issues.apache.org/jira/browse/TEZ-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608811#comment-15608811
]
Hitesh Shah commented on TEZ-3470:
----------------------------------
bq. UTs runs as expected with the existing patch on installing PhantomJS
globally
Does this mean that if it is not globally installed, the build will download
phantomjs locally and UTs will also work in this scenario? Or is there
something wrong with how the non-global install works causing UTs to fail? ( or
is the problem that the local download for ppcle64 is not picking up the
correct bits to download? )
bq. Considering we would have to support both skipTests & maven.test.skip,
please guide on figuring out the best implementation.
Given that we are standardized on v2.1.1 of phantomjs and given that it is
mostly available on all environments, it seems that we could consider skipping
the fix for downloading phantomjs only if tests are enabled? The ember test
approach already handles whether to run tests or not in a correct way for the
most part.
> Tez UI: Make the build work in IBM PPC
> --------------------------------------
>
> Key: TEZ-3470
> URL: https://issues.apache.org/jira/browse/TEZ-3470
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.8.3
> Reporter: Sreenath Somarajapuram
> Assignee: Sreenath Somarajapuram
> Labels: TezUI
> Attachments: TEZ-3470.1.patch, TEZ-3470.2.patch, TEZ-3470.3.patch,
> TEZ-3470.wip.1.patch
>
>
> Current versions of frontend-maven-plugin, node & npm used by the build is
> not functioning as expected in IBM PPC. Following version works, and the
> build must be changed to used the same in a PPC.
> - frontend-maven-plugin : v1.1
> - node : v5.7.0
> - npm : 3.6.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
