You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Doroszlai, Attila (JIRA)" <ji...@apache.org> on 2017/10/02 18:14:00 UTC
[jira] [Updated] (AMBARI-22113) ambari-server/agent python UT fails
[ https://issues.apache.org/jira/browse/AMBARI-22113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doroszlai, Attila updated AMBARI-22113:
---------------------------------------
Fix Version/s: 2.6.0
> ambari-server/agent python UT fails
> -----------------------------------
>
> Key: AMBARI-22113
> URL: https://issues.apache.org/jira/browse/AMBARI-22113
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
> Reporter: Yesha Vora
> Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
>
> {code:title=test cmd}
> cd /grid/0/nobody/workspace/build-support/SOURCES/ambari; git clean -xdf && export MAVEN_OPTS="-Xmx8192m -XX:MaxPermSize=4096m"; /grid/0/nobody/tools/maven/apache-maven-3.3.9/bin/mvn -B -nsu -DforkCount=4 -Dmaven.test.failure.ignore=true -fae clean test{code}
> {code}
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main ........................................ SUCCESS [ 4.941 s]
> [INFO] Apache Ambari Project POM .......................... SUCCESS [ 0.107 s]
> [INFO] Ambari Web ......................................... SUCCESS [01:23 min]
> [INFO] Ambari Views ....................................... SUCCESS [ 3.731 s]
> [INFO] Ambari Admin View .................................. SUCCESS [01:00 min]
> [INFO] utility ............................................ SUCCESS [ 1.566 s]
> [INFO] ambari-metrics ..................................... SUCCESS [ 0.628 s]
> [INFO] Ambari Metrics Common .............................. SUCCESS [ 4.309 s]
> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [ 6.083 s]
> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [ 4.762 s]
> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [ 3.706 s]
> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [ 1.915 s]
> [INFO] Ambari Metrics Storm Sink (Legacy) ................. SUCCESS [ 1.654 s]
> [INFO] Ambari Metrics Collector ........................... SUCCESS [05:53 min]
> [INFO] Ambari Metrics Monitor ............................. SUCCESS [ 3.347 s]
> [INFO] Ambari Metrics Grafana ............................. SUCCESS [ 4.125 s]
> [INFO] Ambari Metrics Assembly ............................ SUCCESS [ 16.521 s]
> [INFO] Ambari Server ...................................... FAILURE [12:34 min]
> [INFO] Ambari Functional Tests ............................ SKIPPED
> [INFO] Ambari Agent ....................................... FAILURE [ 16.861 s]
> [INFO] Ambari Client ...................................... SUCCESS [ 0.071 s]
> [INFO] Ambari Python Client ............................... SUCCESS [ 1.037 s]
> [INFO] Ambari Groovy Client ............................... SUCCESS [ 6.939 s]
> [INFO] Ambari Shell ....................................... SUCCESS [ 0.051 s]
> [INFO] Ambari Python Shell ................................ SUCCESS [ 0.048 s]
> [INFO] Ambari Groovy Shell ................................ SUCCESS [ 3.696 s]
> [INFO] ambari-logsearch ................................... SUCCESS [ 0.332 s]
> [INFO] Ambari Logsearch Appender .......................... SUCCESS [ 0.158 s]
> [INFO] Ambari Logsearch Portal ............................ SUCCESS [ 7.863 s]
> [INFO] Ambari Logsearch Log Feeder ........................ SUCCESS [ 7.417 s]
> [INFO] Ambari Logsearch Solr Client ....................... SUCCESS [ 2.252 s]
> [INFO] Ambari Infra Solr Plugin ........................... SUCCESS [ 1.356 s]
> [INFO] Ambari Logsearch Assembly .......................... SUCCESS [ 0.136 s]
> [INFO] Ambari Logsearch Integration Test .................. SUCCESS [ 0.480 s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 22:39 min
> [INFO] Finished at: 2017-09-29T01:46:23+00:00
> [INFO] Final Memory: 211M/2826M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (python-test) on project ambari-server: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (python-test) on project ambari-agent: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :ambari-server{code}
> Caused by syntax introduced in Python 2.7:
> {code}
> Traceback (most recent call last):
> File "unitTests.py", line 308, in <module>
> sys.exit(main())
> File "unitTests.py", line 260, in main
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in modules]
> File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File "/grid/0/nobody/workspace/build-support/SOURCES/ambari/ambari-server/src/test/python/custom_actions/TestRemoveBits.py", line 28, in <module>
> from stacks.utils.RMFTestCase import *
> File "/grid/0/nobody/workspace/build-support/SOURCES/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py", line 142
> with Environment(basedir, test_mode=True) as RMFTestCase.env,\
> ^
> SyntaxError: invalid syntax{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)