When executing test cases on CrateDB-4.1.8 seven Test Cases are failing

CrateDB
1

Hi all,

I have installed and successfully Build the CrateDB-4.1.8 project. But when I’m executing the Test cases, 7 test cases of TcpTransportTest.java file are failing with below error:

java.lang.AssertionError:
Expected: iterable with items ["[::1]:4300", "[::1]:4301", "[::1]:4302", "127.0.0.1:4300", "127.0.0.1:4301", "127.0.0.1:4302"] in any order
     but: no item matches: "[::1]:4300", "[::1]:4301", "[::1]:4302" in ["127.0.0.1:4300", "127.0.0.1:4301", "127.0.0.1:4302"]
.
.
.
org.elasticsearch.transport.TcpTransportTest > testDefaultSeedAddressesWithSmallProfilePortRange FAILED
    java.lang.AssertionError at TcpTransportTest.java:172

Final Test result:

539 tests completed, 7 failed, 2 skipped

> Task :es:es-server:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':es:es-server:test'.
> There were failing tests. See the report at: file:///home/crate/crate/es/es-server/build/reports/tests/test/index.html

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.5/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 45m 29s
179 actionable tasks: 41 executed, 138 up-to-date

Please guide me, how can I resolve the above error?
Please let me know if any other information is required.

2

Hi @ArqamFarooqui110719,

we don’t support development on old versions (4.1.8 was released on July 2020). I suggest to upgrade to a newer version of CrateDB (e.g. just released, latest & greatest CrateDB 4.7).

Happy to assist with your setup on default branch or latest feature release branch

3

Thanks for your reply and suggestion @jayeff :slight_smile:

Just for Information:
I have resolved the issue by enabling the IPv6 in my environment, earlier it was not enabled.
Now all test cases are executing successfully.

2 Likes