Build: https://ci-builds.apache.org/job/Solr/job/Solr-TestIntegration-9.x/148/

No tests ran.

Build Log:
[...truncated 450 lines...]
#   ERROR: Error from server at 
https://localhost:36340/solr/admin/collections?action=CREATE&name=test&collection.configName=test&numShards=2&nrtReplicas=1&wt=json&version=2.2:
 Underlying core creation failed while creating collection: test
# --
# 
# Please find the SOLR_HOME snapshot for failed test #7 at: 
/home/jenkins/jenkins-slave/workspace/Solr/Solr-TestIntegration-9.x/solr/packaging/build/test-output/failure-snapshots/85-7
# Last output:
# INFO  - 2025-04-05 04:58:21.780; 
org.apache.solr.util.configuration.SSLConfigurations; Setting 
javax.net.ssl.keyStorePassword
# INFO  - 2025-04-05 04:58:21.785; 
org.apache.solr.util.configuration.SSLConfigurations; Setting 
javax.net.ssl.trustStorePassword
# WARN  - 2025-04-05 04:58:24.666; org.apache.solr.common.cloud.SolrZkClient; 
Using default ZkCredentialsInjector. ZkCredentialsInjector is not secure, it 
creates an empty list of credentials which leads to 'OPEN_ACL_UNSAFE' ACLs to 
Zookeeper nodes
# WARN  - 2025-04-05 04:58:25.143; org.apache.solr.common.cloud.SolrZkClient; 
Using default ZkACLProvider. DefaultZkACLProvider is not secure, it creates 
'OPEN_ACL_UNSAFE' ACLs to Zookeeper nodes
ok 86 SOLR-11740 check 'solr stop' connection # in 44456 ms
ok 87 stop command for single port # in 50328 ms
ok 88 start warns about SolrCloud mode if no mode specified # in 24983 ms
ok 89 start warns about SolrCloud mode if --cloud used # in 25954 ms
ok 90 start doesn't warn about SolrCloud mode if --user-managed used # in 21301 
ms
ok 91 check stop command doesn't hang # in 494 ms
ok 92 SOLR-16976 solr starts with remote JMX enabled # in 23061 ms
ok 93 status detects locally running solr # in 28859 ms
ok 94 status with --solr-url from user # in 20474 ms
ok 95 status with --port from user # in 22134 ms
ok 96 status with invalid --solr-url from user # in 20517 ms
ok 97 status with --short format # in 211485 ms
ok 98 --version and -v both return Solr version # in 6806 ms
ok 99 -version and version both return Solr version and deprecation # in 7231 ms
ok 100 short help # in 6825 ms
ok 101 short help is inferred # in 5262 ms
ok 102 long help # in 6275 ms
ok 103 running subcommands with zk is prevented # in 3786 ms
ok 104 listing out files # in 15208 ms
ok 105 connecting to solr via various solr urls and zk hosts # in 39572 ms
ok 106 copying files around # in 42103 ms
ok 107 upconfig # in 6631 ms
ok 108 downconfig # in 5716 ms
ok 109 zkcli.sh gets 'solrhome' from 'solr.home' system property # in 3976 ms
ok 110 zkcli.sh gets 'solrhome' from 'solrhome' command line option # in 4009 ms
ok 111 bin/solr zk cp gets 'solrhome' from '--solr-home' command line option # 
in 4901 ms
ok 112 Cleanup # in 4566 ms

> Task :solr:packaging:integrationTests FAILED

FAILURE: Build failed with an exception.

* Where:
Build file 
'/home/jenkins/jenkins-slave/workspace/Solr/Solr-TestIntegration-9.x/solr/packaging/build.gradle'
 line: 314

* What went wrong:
Execution failed for task ':solr:packaging:integrationTests'.
> Process 'command 
> '/home/jenkins/jenkins-slave/workspace/Solr/Solr-TestIntegration-9.x/solr/packaging/.gradle/node/node_modules/bats/bin/bats''
>  finished with non-zero exit value 1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings 
and determine if they come from your own scripts or plugins.

For more on this, please refer to 
https://docs.gradle.org/8.10/userguide/command_line_interface.html#sec:command_line_warnings
 in the Gradle documentation.

BUILD FAILED in 1h 9m 14s
107 actionable tasks: 107 executed

Publishing build scan...
https://develocity.apache.org/s/fa2ojnbhfyhio

Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to