[ https://issues.apache.org/jira/browse/HDDS-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855372#comment-16855372 ]
Hudson commented on HDDS-1607: ------------------------------ FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16659 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/16659/]) HDDS-1607. Create smoketest for non-secure mapreduce example (#869) (aengineer: rev 1fc359fc101b3ff90c95d22a3f4cfa78b65ae47d) * (add) hadoop-ozone/dist/src/main/compose/ozone-mr/test.sh * (add) hadoop-ozone/dist/src/main/smoketest/createmrenv.robot * (add) hadoop-ozone/dist/src/main/compose/ozone-mr/docker-compose.yaml * (add) hadoop-ozone/dist/src/main/compose/ozone-mr/.env * (add) hadoop-ozone/dist/src/main/compose/ozone-mr/docker-config * (add) hadoop-ozone/dist/src/main/smoketest/mapreduce.robot > Create smoketest for non-secure mapreduce example > ------------------------------------------------- > > Key: HDDS-1607 > URL: https://issues.apache.org/jira/browse/HDDS-1607 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Reporter: Elek, Marton > Assignee: Elek, Marton > Priority: Major > Labels: pull-request-available > Time Spent: 2h > Remaining Estimate: 0h > > We had multiple problems earlier with the classpath separation and the > internal ozonefs classloader. Before fixing all the issues I propose to > create a smoketest to detect if the classpath separation is broken again . > As a first step I created an smoketest/ozone-mr environment (based on the > work of [~xyao], which is secure) and a smoketest > Possible follow-up works: > * Adapt the test.sh for the ozonesecure-mr > * Include test runs with older hadoop versions -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org