Fix NPE for null values in Map and List collection attribute converters #12548
codebuild-ci.yml
on: pull_request
jdk8-build
49m 21s
jdk11-build
40m 23s
jdk17-build
34m 49s
jdk21-build
19m 28s
windows-jdk8-build
35m 54s
native-image-test
23m 38s
sonar-cloud-build
2h 0m
endpoints-tests
35m 26s
brazil-json-validation
16m 12s
migration-tests
9m 14s
Annotations
3 errors and 10 warnings
|
jdk21-build
Build status: FAILED
|
|
sonar-cloud-build
The action 'Run sonar-cloud analysis' has timed out after 120 minutes.
|
|
sonar-cloud-build
Error stopping build: AccessDeniedException: User: arn:aws:sts::131990247566:assumed-role/aws-sdk-for-java-v2-ci-role/GitHubActions is not authorized to perform: codebuild:StopBuild on resource: arn:aws:codebuild:us-west-2:131990247566:project/aws-sdk-java-v2-sonar because no identity-based policy allows the codebuild:StopBuild action
|
|
migration-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
brazil-json-validation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
jdk21-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
native-image-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
jdk17-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
endpoints-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-jdk8-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
jdk11-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
jdk8-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sonar-cloud-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|