Build: https://ci-builds.apache.org/job/Solr/job/Solr-TestIntegration-10.x/179/

No tests ran.

Build Log:
[...truncated 1167 lines...]
#   ERROR: Failed to create collection 'test_stdin' due to: IOException 
occurred when talking to server at: 
http://localhost:44637/solr/admin/collections
# --
# 
# Please find the SOLR_HOME snapshot for failed test #11 at: 
/home/jenkins/jenkins-agent/workspace/Solr/Solr-TestIntegration-10.x/solr/packaging/build/test-output/failure-snapshots/77-11
# Last output:
# Neither --zk-host or --solr-url parameters, nor ZK_HOST env var provided, so 
assuming solr url is http://localhost:44637.
# Neither --zk-host or --solr-url parameters, nor ZK_HOST env var provided, so 
assuming solr url is http://localhost:44637.
# WARNING: Using _default configset. Data driven schema functionality is 
enabled by default, which is
#          NOT RECOMMENDED for production use.
# 
#          To turn it off:
#             curl http://localhost:44637/solr/test_stdin/config -d 
'{"set-user-property": {"update.autoCreateFields":"false"}}'
#          Or:
#             bin/solr config -c test_stdin -s http://localhost:44637 --action 
set-user-property --property update.autoCreateFields --value false
# WARN  - 2026-04-14 17:41:19.769; 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  - 2026-04-14 17:41:19.772; org.apache.solr.common.cloud.SolrZkClient; 
Using default ZkACLProvider. DefaultZkACLProvider is not secure, it creates 
'OPEN_ACL_UNSAFE' ACLs to Zookeeper nodes
# 
# ERROR: Failed to create collection 'test_stdin' due to: IOException occurred 
when talking to server at: http://localhost:44637/solr/admin/collections
not ok 78 verbose echo the Solr response # in 1047 ms
# (from function `assert_output' in file 
.gradle/node/node_modules/bats-assert/src/assert.bash, line 247,
#  in test file test/test_post.bats, line 210)
#   `assert_output --partial "Created collection 'monitors_verbose'"' failed
# 
# -- output does not contain substring --
# substring (1 lines):
#   Created collection 'monitors_verbose'
# output (3 lines):
#   Neither --zk-host or --solr-url parameters, nor ZK_HOST env var provided, 
so assuming solr url is http://localhost:44637.
# 
#   ERROR: Server refused connection at: 
http://localhost:44637/solr/admin/info/system
# --
# 
# Please find the SOLR_HOME snapshot for failed test #12 at: 
/home/jenkins/jenkins-agent/workspace/Solr/Solr-TestIntegration-10.x/solr/packaging/build/test-output/failure-snapshots/78-12
# Last output:
# Neither --zk-host or --solr-url parameters, nor ZK_HOST env var provided, so 
assuming solr url is http://localhost:44637.
# 
# ERROR: Server refused connection at: 
http://localhost:44637/solr/admin/info/system
ok 79 post solr log into solr via cli # in 8440 ms
# Docker artifacts saved to: 
ok 80 Docker SolrCloud rolling upgrade # skip Docker image 
apache/solr-nightly:9.10.0-SNAPSHOT-slim is not available
ok 81 allowPaths - backup # in 14415 ms
ok 82 snapshot lifecycle # in 4453 ms
ok 83 snapshot list # in 3133 ms
ok 84 snapshot describe # in 3064 ms
ok 85 start solr with ssl # in 15033 ms
ok 86 use different hostname when not checking peer-name # in 23366 ms
ok 87 start solr with ssl and auth # in 13811 ms
ok 88 start solr with client truststore and security manager # in 15525 ms
ok 89 start solr with mTLS needed # in 43796 ms
ok 90 start solr with mTLS wanted # in 32441 ms
ok 91 test keystore reload # in 55974 ms
ok 92 SOLR-11740 check 'solr stop' connection # in 15308 ms
ok 93 stop command for single port # in 17439 ms
ok 94 check stop command doesn't hang # in 196 ms
ok 95 SOLR-16976 solr starts with remote JMX enabled # in 7645 ms
ok 96 deprecated system properties converted to modern properties # in 194928 ms
ok 97 start with custom jetty options # in 7704 ms
ok 98 bootstrapping a configset # in 8808 ms
ok 99 status detects locally running solr # in 8943 ms
ok 100 status with --solr-url from user # in 7659 ms
ok 101 status with --port from user # in 7632 ms
ok 102 multiple connection options are prevented # in 797 ms
ok 103 status with invalid --solr-url from user # in 1311 ms
ok 104 status with --short format # in 195666 ms
ok 105 searching solr via locally executed streaming expression # in 1622 ms
ok 106 searching solr via remotely executed streaming expression # in 1195 ms
ok 107 variable interpolation # in 1566 ms
ok 108 searching solr without credentials fails with error # in 1045 ms
ok 109 --version returns Solr version # in 681 ms
ok 110 version as direct tool call still runs # in 683 ms
ok 111 short help # in 707 ms
ok 112 short help is inferred # in 715 ms
ok 113 long help # in 738 ms
ok 114 running subcommands with zk is prevented # in 677 ms
ok 115 listing out files # in 2051 ms
ok 116 connecting to solr via various solr urls and zk hosts # in 7419 ms
ok 117 copying files around # in 10447 ms
ok 118 upconfig # in 2457 ms
ok 119 SOLR-12429 test upconfig fails with symlink # in 1034 ms
ok 120 downconfig # in 1110 ms
ok 121 bin/solr zk cp gets 'solrhome' from '--solr-home' command line option # 
in 1355 ms
ok 122 env var ZK_HOST is honored # in 3027 ms
ok 123 Cleanup # in 1806 ms

> Task :solr:packaging:integrationTests FAILED

FAILURE: Build failed with an exception.

* Where:
Build file 
'/home/jenkins/jenkins-agent/workspace/Solr/Solr-TestIntegration-10.x/solr/packaging/build.gradle'
 line: 339

* What went wrong:
Execution failed for task ':solr:packaging:integrationTests'.
> Process 'command 
> '/home/jenkins/jenkins-agent/workspace/Solr/Solr-TestIntegration-10.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 28m 30s
130 actionable tasks: 130 executed

Publishing Build Scan to Develocity...
https://develocity.apache.org/s/vz2sj3fhciidq

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