You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "lidehua (Jira)" <ji...@apache.org> on 2022/06/14 06:42:00 UTC

[jira] [Commented] (CALCITE-3754) Redis tests fail on ppc64le

    [ https://issues.apache.org/jira/browse/CALCITE-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17553921#comment-17553921 ] 

lidehua commented on CALCITE-3754:
----------------------------------

Is there any progress on this issue? I had the same problem on aarch64.

> Redis tests fail on ppc64le
> ---------------------------
>
>                 Key: CALCITE-3754
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3754
>             Project: Calcite
>          Issue Type: Task
>         Environment: arch: ppc64le
>            Reporter: AK97
>            Priority: Major
>
> I have been trying to build the Apache Calcite on ubuntu:16.04/ppc64le; however, the test cases are failing in Redis module with following error :
> {code:java}
>  Task :redis:test FAILED
> Gradle Test Executor 15 STANDARD_OUT
>     /tmp/1579669916467-0/redis-server-2.8.19: 1: /tmp/1579669916467-0/redis-server-2.8.19: ELF: not found
>     /tmp/1579669916467-0/redis-server-2.8.19: 2: /tmp/1579669916467-0/redis-server-2.8.19: Syntax error: word unexpected (expecting ")")
> FAILURE   0.1sec, org.apache.calcite.adapter.redis.RedisAdapterCaseBase > testSqlWithJoin()
> RedisAdapterCaseBase > testSqlWithJoin() FAILED
>     java.lang.RuntimeException: Can't start redis server. Check logs for details.
>         at redis.embedded.AbstractRedisInstance.awaitRedisServerReady(AbstractRedisInstance.java:61)
>         at redis.embedded.AbstractRedisInstance.start(AbstractRedisInstance.java:39)
>         at redis.embedded.RedisServer.start(RedisServer.java:9)
>         at org.apache.calcite.adapter.redis.RedisCaseBase.createRedisServer(RedisCaseBase.java:48)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:498)
>         at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:675)
>         at org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
>         at org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:125)
> {code}
> Would like some help on understanding the cause for the same . I am running it on a High end VM with good connectivity.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)