[
https://issues.apache.org/jira/browse/OOZIE-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008193#comment-16008193
]
Peter Bacsko commented on OOZIE-2780:
-------------------------------------
I found two more tests that fail consistently because of Hadoop 2.6.0 upgrade:
{noformat}
Running org.apache.oozie.util.TestZKUtilsWithSecurity
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 45.108 sec <<<
FAILURE!
Results :
Tests in error:
testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity):
org/apache/commons/io/Charsets
testCheckAndSetACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): Another
CacheManager with same name 'apacheds' already exists in the same VM. Please
provide unique names for each CacheManager in the config or do one of
following:(..)
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
{noformat}
> Upgrade minimum Hadoop version to 2.6.0
> ---------------------------------------
>
> Key: OOZIE-2780
> URL: https://issues.apache.org/jira/browse/OOZIE-2780
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.3.0
> Reporter: Artem Ervits
> Assignee: Artem Ervits
> Priority: Minor
> Labels: newbie
> Fix For: 5.0.0
>
> Attachments: OOZIE-2780-0.patch, OOZIE-2780-1.patch,
> OOZIE-2780-2.patch
>
>
> I'd like to contribute an fs action enhancement to modify extended attributes
> to core but methods to change extended attributes is not available in
> hadoop-common < 2.6.0. Currently hadoop-common is at 2.4. I am contributing a
> patch to bump to 2.6 but so far I haven't been able to generate a clean test
> as tests in core module fail randomly. On the first run, I had a failure on
> {code} Failed tests:
> testCheckAfterActionDelete(org.apache.oozie.service.TestHAPartitionDependencyManagerService):
> Expected: <null> but was: [0000000-170123095541655-oozie-aerv-C@1]{code}
> and on second run
> {code}Failed tests: testWaitFor(org.apache.oozie.test.TestXTestCase):
> expected:<1000.0> but was:<2036.0>{code}
> I can't tell whether it is due to my patch?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
