stresstest.sh takes optional go build flags

[AndersonQ]

Proposed commit message

stresstest.sh takes optional go build flags

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.

Disruptive User Impact

• N/A

How to test this PR locally

use stresstest.sh to stress test an integration test

cd filebeat
../script/stresstest.sh --tags integration ./testing/integration/ TestFilebeat -p 1

Related issues

• N/A

Use cases

use stresstest.sh with integration tests

Logs

❯ ../script/stresstest.sh --tags integration ./testing/integration/ TestFilebeat -p 1
5s: 0 runs so far, 0 failures, 1 active
10s: 0 runs so far, 0 failures, 1 active
15s: 0 runs so far, 0 failures, 1 active
20s: 0 runs so far, 0 failures, 1 active
25s: 0 runs so far, 0 failures, 1 active
30s: 0 runs so far, 0 failures, 1 active
35s: 1 runs so far, 0 failures, 1 active
40s: 1 runs so far, 0 failures, 1 active
45s: 1 runs so far, 0 failures, 1 active
50s: 1 runs so far, 0 failures, 1 active
55s: 1 runs so far, 0 failures, 1 active
1m0s: 1 runs so far, 0 failures, 1 active
1m5s: 2 runs so far, 0 failures, 1 active
1m10s: 2 runs so far, 0 failures, 1 active
1m15s: 2 runs so far, 0 failures, 1 active
1m20s: 2 runs so far, 0 failures, 1 active
1m25s: 2 runs so far, 0 failures, 1 active
1m30s: 3 runs so far, 0 failures, 1 active
1m35s: 3 runs so far, 0 failures, 1 active

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

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