Support JDK-23 (build time and runtime)

[reta]

Description

Support JDK-23 (build time and runtime)

Related Issues

Part of #16255

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

❌ Gradle check result for 1e6c67a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 1e6c67a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 1e6c67a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[peternied]

@reta Looks like you are iterating, LMK when you'd like a deeper look - fundamentally I approve!

[github-actions]

❌ Gradle check result for 070914c: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for ea1c382: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 5714c24: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 5714c24: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 5714c24: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 2d1efcb: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[reta]

@peternied all set! thank you!

[reta]

The check is green but GA script is stuck:

parse error: Invalid numeric literal at line 4, column 14
parse error: Invalid numeric literal at line 1, column 10
parse error: Invalid numeric literal at line 4, column 14
parse error: Invalid numeric literal at line 4, column 14
parse error: Invalid numeric literal at line 4, column 14
parse error: Invalid numeric literal at line 4, column 14
Workflow running status :Attempt 1/10 failed. The jq processing failed with exit code: 4. Retrying...
Attempt 2/10 failed. The jq processing failed with exit code: 4. Retrying...
Attempt 3/10 failed. The jq processing failed with exit code: 4. Retrying...
Attempt 4/10 failed. The jq processing failed with exit code: 4. Retrying...
Attempt 5/10 failed. The jq processing failed with exit code: 4. Retrying...
Attempt 6/10 failed. The jq processing failed with exit code: 4. Retrying...
true
Complete the run, checking results now......
Use queue information to find build number in Jenkins if available
parse error: Invalid numeric literal at line 5, column 12
WORKFLOW_URL

• https://build.ci.opensearch.org/job/gradle-check/49237/

[github-actions]

❌ Gradle check result for e5ac86f: null

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❕ Gradle check result for e5ac86f: UNSTABLE

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.03%. Comparing base (691f725) to head (e5ac86f).
Report is 2 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #16257      +/-   ##
============================================
- Coverage     72.06%   72.03%   -0.04%     
+ Complexity    64822    64804      -18     
============================================
  Files          5308     5308              
  Lines        302574   302565       -9     
  Branches      43710    43710              
============================================
- Hits         218048   217945     -103     
- Misses        66648    66735      +87     
- Partials      17878    17885       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[peternied]

Thanks for reviewing this @msfroh

[yuye-aws]

@reta Can we backport this version update change to 2.x?

[yuye-aws]

Let me provide some context here. I'm working on the skills repo. I've created a PR to fix the CI error by bumping the version of bytebuddy, but it is very strange that its backport-2.x PR meets with the version conflict error:

* What went wrong:
Execution failed for task ':compileTestJava'.
> Could not resolve all dependencies for configuration ':testCompileClasspath'.
   > Conflict found for the following module:
       - net.bytebuddy:byte-buddy between versions 1.15.10 and 1.15.4

Do you have any hint on why? I do not have much context on these dependencies.

[reta]

The 2.x is on 15.10 as well (#16657), I will take a look shortly why the CI for the skills repo repo fails.