-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the Bootstrap check test failure on Windows. #15975
Conversation
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
💚 Build Succeeded
cc @mashhurs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
I tested this, by merging your PR to my open PR that implements the job split in Buildkite and after triggering a new Windows job everything passed: https://buildkite.com/elastic/logstash-windows-jdk-matrix-pipeline/builds/123#_
Note that this will need to be backported, if we intended to backport the Buildkite job split in #15888 to older branches. |
Feel free to backport to the branches you are considering to split. |
@logstashmachine backport 8.13 |
@logstashmachine backport 8.12 |
(cherry picked from commit 1963714)
(cherry picked from commit 1963714)
@logstashmachine backport 7.17 |
(cherry picked from commit 1963714)
(cherry picked from commit 1963714) Co-authored-by: Mashhur <[email protected]>
(cherry picked from commit 1963714) Co-authored-by: Mashhur <[email protected]>
(cherry picked from commit 1963714) Co-authored-by: Mashhur <[email protected]>
Release notes
[rn:skip]
What does this PR do?
Fixes the Bootstrap check test failure on Windows.
.\gradlew clean test --console=plain --no-daemon --no-build-cache --info
result which I believe same as.\ci\unit_tests.ps1
or./gradle.bat test
Why is it important/What is the impact to the user?
Non-user facing change.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)[ ] I have added tests that prove my fix is effective or that my feature worksAuthor's Checklist
How to test this PR locally
Related issues
LogStash::ConfigManagement::BootstrapCheck
raises aLogStash::BootstrapCheckError
when running ruby tests in isolation on Windows #15890Logs