[
https://issues.apache.org/jira/browse/TEZ-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215463#comment-15215463
]
TezQA commented on TEZ-3182:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12795763/TEZ-3182.1.patch
against master revision 182c997.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1596//console
This message is automatically generated.
> linux superuser use maven compile bower always fail
> ---------------------------------------------------
>
> Key: TEZ-3182
> URL: https://issues.apache.org/jira/browse/TEZ-3182
> Project: Apache Tez
> Issue Type: Bug
> Components: UI
> Affects Versions: 0.6.2, 0.8.2
> Environment: linux rh6
> Reporter: shenxianqiang
> Assignee: shenxianqiang
> Priority: Trivial
> Attachments: TEZ-3182.1.patch, TEZ-3182.patch
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> When I am root. Using 'mvn clean package -DskipTests=true' command always
> fail.
> [INFO] --- exec-maven-plugin:1.3.2:exec (Bower install) @ tez-ui ---
> bower ESUDO Cannot be run with sudo
> Additional error details:
> Since bower is a user command, there is no need to execute it with superuser
> permissions.
> If you're having permission errors when using bower without sudo, please
> spend a few minutes learning more about how your system should work and make
> any necessary repairs.
> http://www.joyent.com/blog/installing-node-and-npm
> https://gist.github.com/isaacs/579814
> You can however run a command with sudo using --allow-root option
> I have to modify pom.xml.Why not modify pom.xml in future?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
