fix libbeat stress-tests

[sharbuz]

What is the problem this PR solves?

Jenkins->Buildkite pipelines migration

The PR fixes the issues:

[2024-02-05T16:13:59.159Z] + make STRESS_TEST_OPTIONS=-timeout=20m -race -v -parallel 1 -C libbeat stress-tests
[2024-02-05T16:13:59.159Z] make: Entering directory '/var/lib/jenkins/workspace/main-2287-c122c791-d81b-466c-8ad7-4cbbc004111d/src/github.com/elastic/beats/libbeat'
[2024-02-05T16:13:59.587Z] dirname: missing operand
[2024-02-05T16:13:59.588Z] Try 'dirname --help' for more information.
[2024-02-05T16:13:59.746Z] dirname: missing operand
[2024-02-05T16:13:59.746Z] Try 'dirname --help' for more information.
[2024-02-05T16:13:59.746Z] if [ -n '' ]; then \
[2024-02-05T16:13:59.746Z] 	go test --tags=stresstest -timeout=20m -race -v -parallel 1 ; \
[2024-02-05T16:13:59.746Z] fi
[2024-02-05T16:13:59.746Z] make: Leaving directory '/var/lib/jenkins/workspace/main-2287-c122c791-d81b-466c-8ad7-4cbbc004111d/src/github.com/elastic/beats/libbeat'

How does this PR solve the problem?

Change the approach of finding a place for stress tests.

Related issues

The metricbeat issue is solved in the #37725

https://github.com/elastic/ingest-dev/issues/1693

[botelastic]

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

[v1v]

Thanks!

[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: 133 min 37 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!)

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 86196b8

History

• 💔 Build #2519 failed 7d8cdd6

cc @sharbuz

[jlind23]

LGTM