Skip to content

Conversation

kruskall
Copy link
Member

Do not write status header before processing data or it could lead to
flaky tests due to a race when reading apmServerInternals.Data.
Add proper logging and return early if an error was returned.

Do not write status header before processing data or it could lead to
flaky tests due to a race when reading apmServerInternals.Data.
Add proper logging and return early if an error was returned.
@github-actions github-actions bot added the aws-λ-extension AWS Lambda Extension label Aug 31, 2022
@ghost
Copy link

ghost commented Aug 31, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-08-31T15:47:03.954+0000

  • Duration: 8 min 33 sec

Test stats 🧪

Test Results
Failed 0
Passed 160
Skipped 2
Total 162

🤖 GitHub comments

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

  • /test : Re-trigger the build.

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

@kruskall kruskall merged commit 1873d34 into elastic:main Sep 1, 2022
@kruskall kruskall deleted the fix/flaky-main-test branch September 1, 2022 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aws-λ-extension AWS Lambda Extension

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants