auditbeat - skip TestExeObjParser on CI

[andrewkroh]

Proposed commit message

TestExeObjParser fails on Windows because Defender is removing the testdata that is required by the test. This adds a conditional test skip for CI when those files are missing.

Closes #38211

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.

[elasticmachine]

Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @andrewkroh? 🙏.
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 Succeeded

• Buildkite Build
• Commit: 85e62bf

cc @andrewkroh

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 85e62bf

cc @andrewkroh

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 85e62bf

cc @andrewkroh

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 85e62bf

cc @andrewkroh

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 85e62bf

cc @andrewkroh

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 85e62bf

cc @andrewkroh

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 85e62bf

cc @andrewkroh

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 85e62bf

cc @andrewkroh

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 85e62bf

Failed CI Steps

• :windows:-family/core-windows-2016 Unit Tests
• :windows:-family/core-windows-2022 Unit Tests

History

cc @andrewkroh

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 85e62bf

Failed CI Steps

• :windows: Unit Tests / family/core-windows-2016
• :windows: Unit Tests / family/core-windows-2022

History

cc @andrewkroh

[elasticmachine]

💚 Build Succeeded

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

Expand to view the summary

Build stats

• Duration: 47 min 3 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 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!)

[pierrehilbert]

I added some backports as it was failing on the other branches.