[fix] skip SQL Server integration test on arm64 - #4253
Merged
Conversation
Aias00
approved these changes
Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's changed?
SqlServerJdbcTemplateIntegrationTestcannot run on arm64 hosts. Microsoft ships no arm64 image for SQL Server on Linux (2017-latest,2019-latestand2022-latestare all amd64-only), so under emulationsqlservrcrashes on startup and never logs "SQL Server is now ready for client connections". The wait strategy then times out after ~68 minutes. Rosetta does not help.This skips the class on arm64 via
Assumptions.assumeFalse, checked before the Docker probe so no container is started. The full matrix still runs on the amd64 CI runners, so no coverage is lost.On an Apple Silicon host: 4053 s error → 0.03 s skip.
Checklist