Update jruby to 10.0.6.0

[donoghuc]

Release notes

Update jruby to 10.0.6.0

What does this PR do?

Take up the latest 10.0 jruby release. Reference: https://github.com/jruby/jruby/releases/tag/10.0.6.0

Closes https://github.com/elastic/ingest-dev/issues/8650

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

[donoghuc]

run exhaustive tests

[mergify]

This pull request does not have a backport label. Could you fix it @donoghuc? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• If no backport is necessary, please add the backport-skip label

[github-actions]

TL;DR

Java unit compilation is failing after the JRuby 10.0.6.0 bump because RubyBasicObjectSerializerTest now triggers a JRuby deprecation warning, and the Java test compile runs with -Werror.

Remediation

• Replace new RubyArray<>(RUBY, 2) in logstash-core/src/test/java/org/logstash/log/RubyBasicObjectSerializerTest.java with the non-deprecated JRuby factory, for example RubyArray.newArray(context, 2) using the existing ThreadContext context.
• Validate with ./gradlew :logstash-core:javaTests --tests org.logstash.log.RubyBasicObjectSerializerTest and the FIPS Java test target if available.

Investigation details

Root Cause

The PR only changes versions.yml to move JRuby from 10.0.5.0 to 10.0.6.0. In JRuby 10.0.6.0, RubyArray(Ruby,int) is deprecated, and Logstash's Java compile treats warnings as errors.

The failing source is:

// logstash-core/src/test/java/org/logstash/log/RubyBasicObjectSerializerTest.java:78-80
final ThreadContext context = RUBY.getCurrentContext();
final RubyArray<RubySymbol> rubyArray = new RubyArray<>(RUBY, 2);
rubyArray.push(context, RubySymbol.newSymbol(RUBY, "one"));

JRuby 10.0.6.0 provides RubyArray.newArray(ThreadContext, int) for this allocation path, and the existing test already has the needed ThreadContext.

Evidence

• Build: https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/5014
• Job/step: :java: Java unit tests, task :logstash-core:compileTestJava
• Key log excerpt:

/logstash/logstash-core/src/test/java/org/logstash/log/RubyBasicObjectSerializerTest.java:79: warning: [deprecation] RubyArray(Ruby,int) in RubyArray has been deprecated
        final RubyArray rubyArray = new RubyArray<>(RUBY, 2);
                                                ^
error: warnings found and -Werror specified
> Task :logstash-core:compileTestJava FAILED

The FIPS Java unit job shows the same compiler failure at the same source line, so this is a deterministic compile break rather than a flaky test.

Verification

Not run locally; this is a read-only CI detective workflow. The diagnosis is based on the decoded Buildkite job logs and the PR diff.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• buildkitecloud.s3.amazonaws.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "buildkitecloud.s3.amazonaws.com"

See Network Configuration for more information.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[donoghuc]

run exhaustive tests

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: 92edc28

History

• 💔 Build #5014 failed b1ec296