cgivre opened a new pull request, #3060: URL: https://github.com/apache/drill/pull/3060
## Description The Splunk unit tests have been failing consistently on CI. The `splunk/splunk:9.3` tag was republished on 2026-07-01 to point at 9.3.14. Identical test code passed on 2026-06-26 against 9.3.13 and fails on 9.3.14, so the image is the only variable. 9.3.14 serves HTTPS on the management port despite `SPLUNKD_SSL_ENABLE=false`, so the plaintext client failed every connection with `Unexpected end of file from server`. Disabling splunkd SSL is a path Splunk has regressed repeatedly ([splunk/docker-splunk#639](https://github.com/splunk/docker-splunk/issues/639), still open), so this talks to the default HTTPS listener instead and turns off certificate and hostname validation for the self-signed container cert. The patch version is now pinned so an upstream push cannot break the build on its own. Also corrects the constructor argument comment, which listed five names for six values and hid `validateHostname=true` on the shared-user config. ## Changes - `SplunkTestSuite`: pin image to `splunk/splunk:9.3.14`, drop `SPLUNKD_SSL_ENABLE=false`, connect over `https`, and set `validateCertificates=false` / `validateHostname=false` on both plugin configs. ## Documentation No user-facing changes; test-only. ## Testing `contrib/storage-splunk` test sources compile. The suite requires Docker to run the Splunk container. Cherry-picked from https://github.com/apache/drill/pull/3037 (commit 24cbbdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
