sineflow / ElasticsearchBundle

88%

main: 87%

LAST BUILD ON BRANCH 8.1

branch: 8.1

CHANGE BRANCH

x

Reset

Sync Branches

• 8.1
• 0.5.x
• 2016-03-23-scanscroll
• 2016-07-09-es2
• 2017-05-26-track-entities
• 2018-02-06-array-access
• 2018-02-20-upgrade
• 2018-03-15-es2
• 2018-03-16-es5
• 2019-06-24-remove-types-support
• 2019-07-18-sf4-support
• 2019-08-01-es7
• 2019-08-15-remove-deprecations
• 2019-10-22-knp-fix
• 2022-05-05-reorganise-structure
• 2023-10-09-github-actions
• 2025-05-13-attributes-support
• 2026-06-12-scroll-improvement
• 6.4
• 6.5
• 7.0
• 7.1
• 7.2
• 8.0
• 8.2
• 9.0
• main
• master
• refs/pull/19/merge
• v.0.5.0
• v0.5.0
• v0.6.0
• v0.7.0
• v0.7.1
• v0.8.0
• v0.9.0
• v0.9.1
• v0.9.2
• v0.9.3
• v0.9.4
• v0.9.5
• v0.9.6
• v0.9.7
• v6.2.0
• v6.2.1
• v6.2.2
• v6.3.0
• v6.3.1
• v6.3.2
• v6.4.0
• v6.4.1
• v6.4.2
• v6.5.0
• v7.0.0
• v7.1.1
• v7.1.2
• v7.1.3
• v7.1.5
• v7.1.6
• v8.0.0
• v8.0.1
• v8.1.0
• v8.1.1
• v8.1.2
• v8.1.3
• v8.1.4
• v8.1.5
• v8.2.0
• v8.2.1
• v9.0.0

Build # 27435426137

Build Type

push

github

Committed by pmishev

Commit Message

Fix CI tests failing on current GitHub Actions runners

The JDKs bundled in the older ES images (8.0, 8.1) are affected by
JDK-8287073 and crash with an NPE in CgroupV2Subsystem on hosts with a
cgroup v2 layout they cannot parse, such as the current GitHub Actions
runners (https://github.com/actions/runner-images/issues/13684).

Work around it by disabling JVM container awareness via _JAVA_OPTIONS,
which - unlike ES_JAVA_OPTS and JAVA_TOOL_OPTIONS - reaches every JVM the
image starts, including the options-parsing launcher. This is safe, as the
heap size is set explicitly, so nothing relies on container memory
detection.

Also output the Elasticsearch container logs in CI when the container
fails to start, so such failures are not blind in the future.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Coverage Stats

1654 of 1871 relevant lines covered (88.4%)

121.9 hits per line