[jira] [Updated] (OOZIE-2043) Misc test failures against JDK8
[ https://issues.apache.org/jira/browse/OOZIE-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated OOZIE-2043: --- Fix Version/s: (was: trunk) 4.2 > Misc test failures against JDK8 > --- > > Key: OOZIE-2043 > URL: https://issues.apache.org/jira/browse/OOZIE-2043 > Project: Oozie > Issue Type: Bug > Components: tests >Affects Versions: trunk >Reporter: Robert Kanter >Assignee: Robert Kanter > Fix For: 4.2 > > Attachments: OOZIE-2043.patch, OOZIE-2043.patch > > > Using the below procedure, I built Oozie with Java 7 and then built and ran > the tests with Java 8: > - set java 7 > - {{mvn clean test -DskipTests}} > - {{find . -name test-classes | grep target/test-classes | xargs rm -rf}} > // Delete test classes > - set java 8 > - {{mvn test -DtargetJavaVersion=1.8}} > There were 3 test failures: > - org.apache.oozie.coord.TestHCatELFunctions.testDataOutPartitions > -- it was expecting {{'region=euro,datastamp=20130230'}} but now got > {{'datastamp=20130230,region=euro'}} > - org.apache.oozie.util.TestELConstantsFunctions.testAppendAll > -- Java 8 changes the behavior of the String.split method to not include a > leading empty String if the pattern matches the front of the String. To > remain backwards compatible, the solution here was to emulate this behavior > so the appendAll method behaves the same as it did with Java 6 and 7. > - > org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser.testForkJoinMismatch > -- it was checking a parameterized error message where the order of the > parameters switched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2043) Misc test failures against JDK8
[ https://issues.apache.org/jira/browse/OOZIE-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated OOZIE-2043: - Attachment: OOZIE-2043.patch The new patch fixes the output order. Though after reading the documentation, in hindsight, I'm not sure this really matters because this is supposed to be a list of {{key=value}} pairs, whose order doesn't appear to matter as far as I can tell. Anyway, this makes the test more consistent. [~rohini], can you take another look? > Misc test failures against JDK8 > --- > > Key: OOZIE-2043 > URL: https://issues.apache.org/jira/browse/OOZIE-2043 > Project: Oozie > Issue Type: Bug > Components: tests >Affects Versions: trunk >Reporter: Robert Kanter >Assignee: Robert Kanter > Fix For: trunk > > Attachments: OOZIE-2043.patch, OOZIE-2043.patch > > > Using the below procedure, I built Oozie with Java 7 and then built and ran > the tests with Java 8: > - set java 7 > - {{mvn clean test -DskipTests}} > - {{find . -name test-classes | grep target/test-classes | xargs rm -rf}} > // Delete test classes > - set java 8 > - {{mvn test -DtargetJavaVersion=1.8}} > There were 3 test failures: > - org.apache.oozie.coord.TestHCatELFunctions.testDataOutPartitions > -- it was expecting {{'region=euro,datastamp=20130230'}} but now got > {{'datastamp=20130230,region=euro'}} > - org.apache.oozie.util.TestELConstantsFunctions.testAppendAll > -- Java 8 changes the behavior of the String.split method to not include a > leading empty String if the pattern matches the front of the String. To > remain backwards compatible, the solution here was to emulate this behavior > so the appendAll method behaves the same as it did with Java 6 and 7. > - > org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser.testForkJoinMismatch > -- it was checking a parameterized error message where the order of the > parameters switched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2043) Misc test failures against JDK8
[ https://issues.apache.org/jira/browse/OOZIE-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated OOZIE-2043: - Attachment: OOZIE-2043.patch > Misc test failures against JDK8 > --- > > Key: OOZIE-2043 > URL: https://issues.apache.org/jira/browse/OOZIE-2043 > Project: Oozie > Issue Type: Bug > Components: tests >Affects Versions: trunk >Reporter: Robert Kanter >Assignee: Robert Kanter > Fix For: trunk > > Attachments: OOZIE-2043.patch > > > Using the below procedure, I built Oozie with Java 7 and then built and ran > the tests with Java 8: > - set java 7 > - {{mvn clean test -DskipTests}} > - {{find . -name test-classes | grep target/test-classes | xargs rm -rf}} > // Delete test classes > - set java 8 > - {{mvn test -DtargetJavaVersion=1.8}} > There were 3 test failures: > - org.apache.oozie.coord.TestHCatELFunctions.testDataOutPartitions > -- it was expecting {{'region=euro,datastamp=20130230'}} but now got > {{'datastamp=20130230,region=euro'}} > - org.apache.oozie.util.TestELConstantsFunctions.testAppendAll > -- Java 8 changes the behavior of the String.split method to not include a > leading empty String if the pattern matches the front of the String. To > remain backwards compatible, the solution here was to emulate this behavior > so the appendAll method behaves the same as it did with Java 6 and 7. > - > org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser.testForkJoinMismatch > -- it was checking a parameterized error message where the order of the > parameters switched -- This message was sent by Atlassian JIRA (v6.3.4#6332)