[
https://issues.apache.org/jira/browse/HADOOP-17224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246526#comment-17246526
]
Ayush Saxena commented on HADOOP-17224:
---------------------------------------
Yahh, sounds good to me, we can commit over weekend and observe, if we get some
EC related failures, or some suspicious test failures, or change in reasons of
test failures, we can revert back by Monday. If there are failures, then that
would be some bug itself in our code, which we need to fix. As of now, we don't
know what to do here. Atleast we would have the traces and the names of the
tests which are problematic, in case if they are...
[~ahussein] does that make sense?
[~tasanuma] will it be possible to run the entire test suite while raising the
PR? May be just increasing the timeout in the Jenkinsfile or touching the
hadoop-project/pom.xml should do the trick.
> Install Intel ISA-L library in Dockerfile
> -----------------------------------------
>
> Key: HADOOP-17224
> URL: https://issues.apache.org/jira/browse/HADOOP-17224
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Takanobu Asanuma
> Assignee: Takanobu Asanuma
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, there is not isa-l library in the docker container, and jenkins
> skips the natvie tests, TestNativeRSRawCoder and TestNativeXORRawCoder.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
