[
https://issues.apache.org/jira/browse/OOZIE-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426349#comment-17426349
]
Dénes Bodó commented on OOZIE-3639:
-----------------------------------
Hey [~mgrigorov]
Thanks for the details and the patch. Let me test your change in a different
environment. I can do that next week.
Regarding Oozie patches: when you upload a patch file to the Jira a Jenkins job
notices it and starts this:
[https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/] which runs the checks
and tests using Maven. All the code used testin is in the Oozie repository.
Pull requests are not used for Oozie, but this could change in the future.
{quote}Is Oozie team interested in adding Linux ARM64 as a CI agent ? I could
help providing a dedicated VM! What CI system does the project use ?
{quote}
Let's discuss this topic on [[email protected]|mailto:[email protected]]
list. I think it would be a good idea to support other architecture out of box.
Right now Oozie is capable of running on any machine if there is Java installed
so only the low level libs can be different. Should we pack all of them with
Oozie and pray not to cause issues or create a new build profile which selects
the low level dependencies at build time? I think we should discuss this topic.
Currently Oozie uses the CI provided by Apache: automatic build, tests and code
check runs against every patch uploaded to the Jiras.
> Build failure on Linux ARM64
> ----------------------------
>
> Key: OOZIE-3639
> URL: https://issues.apache.org/jira/browse/OOZIE-3639
> Project: Oozie
> Issue Type: Bug
> Components: build
> Affects Versions: 5.2.1
> Reporter: Martin Tzvetanov Grigorov
> Assignee: Martin Tzvetanov Grigorov
> Priority: Major
>
> Trying to build Apache Oozie on Linux ARM64 fails due:
> # An old version of snappy-java library (transitive dependency of Apache
> Spark):
> {code:java}
> [ERROR] testMain(org.apache.oozie.action.hadoop.TestSparkMain) Time elapsed:
> 3.512 s <<< ERROR!
> java.lang.IllegalArgumentException: org.xerial.snappy.SnappyError:
> [FAILED_TO_LOAD_NATIVE_LIBRARY] no native library is found for os.name=Linux
> and os.arch=aarch64
> at
> org.apache.spark.io.SnappyCompressionCodec$.liftedTree1$1(CompressionCodec.scala:171)
> at
> org.apache.spark.io.SnappyCompressionCodec$.org$apache$spark$io$SnappyCompressionCodec$$version$lzycompute(CompressionCodec.scala:168)
> at
> org.apache.spark.io.SnappyCompressionCodec$.org$apache$spark$io$SnappyCompressionCodec$$version(CompressionCodec.scala:168)
> at
> org.apache.spark.io.SnappyCompressionCodec.<init>(CompressionCodec.scala:152)
> ...
> Caused by: org.xerial.snappy.SnappyError: [FAILED_TO_LOAD_NATIVE_LIBRARY] no
> native library is found for os.name=Linux and os.arch=aarch64
> at
> org.xerial.snappy.SnappyLoader.findNativeLibrary(SnappyLoader.java:331)
> at
> org.xerial.snappy.SnappyLoader.loadNativeLibrary(SnappyLoader.java:171)
> at org.xerial.snappy.SnappyLoader.load(SnappyLoader.java:152)
> at org.xerial.snappy.Snappy.<clinit>(Snappy.java:46)
> at
> org.apache.spark.io.SnappyCompressionCodec$.liftedTree1$1(CompressionCodec.scala:169)
> ... 80 more{code}
> Adding a dependency management for snappy-java to use
> org.xerial.snappy:snappy-java:1.1.8.4 fixes it!
> 2. Test failure in TestPyspark:
> {code:java}
> [ERROR] testPyspark(org.apache.oozie.action.hadoop.TestPyspark) Time
> elapsed: 59.513 s <<< FAILURE!
> junit.framework.ComparisonFailure: expected:<[SUCCEED]ED> but
> was:<[FAILED/KILL]ED>
> at junit.framework.Assert.assertEquals(Assert.java:100)
> at junit.framework.Assert.assertEquals(Assert.java:107)
> at junit.framework.TestCase.assertEquals(TestCase.java:260)
> at
> org.apache.oozie.action.hadoop.TestPyspark.testPysparkHelper(TestPyspark.java:107)
> at
> org.apache.oozie.action.hadoop.TestPyspark.testPyspark(TestPyspark.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ... {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
