Fix CI issues

[shmsr]

Proposed commit message

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[botelastic]

This pull request doesn't have a Team:<team> label.

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @shmsr? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-03-27T21:17:39.483+0000

• Duration: 132 min 34 sec

Test stats 🧪

Test	Results
Failed	0
Passed	30614
Skipped	959
Total	31573

Steps errors

Expand to view the steps failures

Show only the first 10 steps failures

x-pack/winlogbeat-build-windows-2019 - mage build unitTest

• Took 10 min 5 sec . View more details here
• Description: mage build unitTest

x-pack/winlogbeat-build-windows-2019 - mage build unitTest

• Took 2 min 40 sec . View more details here
• Description: mage build unitTest

x-pack/winlogbeat-build-windows-2019 - mage build unitTest

• Took 2 min 39 sec . View more details here
• Description: mage build unitTest

x-pack/winlogbeat-windows-2022-windows-2022 - mage build unitTest

• Took 9 min 28 sec . View more details here
• Description: mage build unitTest

x-pack/winlogbeat-windows-2022-windows-2022 - mage build unitTest

• Took 1 min 30 sec . View more details here
• Description: mage build unitTest

x-pack/winlogbeat-windows-2022-windows-2022 - mage build unitTest

• Took 1 min 30 sec . View more details here
• Description: mage build unitTest

x-pack/winlogbeat-windows-2016-windows-2016 - mage build unitTest

• Took 9 min 18 sec . View more details here
• Description: mage build unitTest

x-pack/winlogbeat-windows-2016-windows-2016 - mage build unitTest

• Took 2 min 32 sec . View more details here
• Description: mage build unitTest

x-pack/winlogbeat-windows-2016-windows-2016 - mage build unitTest

• Took 2 min 31 sec . View more details here
• Description: mage build unitTest

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'hudson.AbortException: script returned exit code 1'

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b fix-ci-failure upstream/fix-ci-failure
git merge upstream/8.13
git push upstream fix-ci-failure

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @shmsr? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b fix-ci-failure upstream/fix-ci-failure
git merge upstream/main
git push upstream fix-ci-failure