[CI] StackTemplateRegistryTests testRegistryIsUpToDate failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic-platform-support #11349 / windows-2025_checkpart2_platform-support-windows
• elasticsearch-periodic-platform-support #11349 / windows-2022_checkpart2_platform-support-windows
• elasticsearch-periodic-platform-support #11345 / windows-2025_checkpart2_platform-support-windows
• elasticsearch-periodic-platform-support #11341 / windows-2022_checkpart2_platform-support-windows
• elasticsearch-periodic-platform-support #11341 / windows-2025_checkpart2_platform-support-windows
• elasticsearch-periodic-platform-support #11337 / windows-2025_checkpart2_platform-support-windows
• elasticsearch-periodic-platform-support #11333 / windows-2025_checkpart2_platform-support-windows
• elasticsearch-periodic-platform-support #11329 / windows-2022_checkpart2_platform-support-windows
• elasticsearch-periodic-platform-support #11325 / windows-2025_checkpart2_platform-support-windows
• elasticsearch-periodic-platform-support #11325 / windows-2022_checkpart2_platform-support-windows

Reproduction Line:

gradlew ":x-pack:plugin:stack:test" --tests "org.elasticsearch.xpack.stack.StackTemplateRegistryTests.testRegistryIsUpToDate" -Dtests.seed=A1C795A17289BCAF -Dtests.locale=en-IO -Dtests.timezone=America/Argentina/Catamarca -Druntime.java=25

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.junit.ComparisonFailure: The StackTemplateRegistry.REGISTRY_VERSION must be incremented when templates are changed. Please update REGISTRY_VERSION to 20 and update COMPUTED_CHECKSUM to "7a27b784" expected:<[228d8ef7]> but was:<[7a27b784]>

Issue Reasons:

• [main] 2 consecutive failures in test testRegistryIsUpToDate
• [main] 8 consecutive failures in step windows-2025_checkpart2_platform-support-windows
• [main] 8 consecutive failures in step windows-2022_checkpart2_platform-support-windows
• [main] 16 failures in test testRegistryIsUpToDate (1.7% fail rate in 963 executions)
• [main] 8 failures in step windows-2025_checkpart2_platform-support-windows (100.0% fail rate in 8 executions)
• [main] 8 failures in step windows-2022_checkpart2_platform-support-windows (100.0% fail rate in 8 executions)
• [main] 11 failures in pipeline elasticsearch-periodic-platform-support (100.0% fail rate in 11 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

[elasticsearchmachine]

Pinging @elastic/es-data-management (Team:Data Management)

[nielsbauman]

@eyalkoren looks like #136666 is causing some issues. Note that both test failures occurred on Windows. Could it be that the checksum algorithm you chose behaves differently on Windows? It would be great if you could have a look when you have time, thanks!

[eyalkoren]

The checksum algorithm is implemented in java.util.zip.CRC32, so I would be surprised if it's the cause of the inconsistency.
I think it's more likely that the binary representation is the cause (e.g. if the CI job on Windows uses Git with its default configurations to clone the repo, the line endings would be different).
Either way, the entire purpose of this test is to remind the PR author to increment the version, so the best way to fix this issue is to disable this specific test on Windows. I will try to see if that is possible

[eyalkoren]

See proposed fix: #137307