-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing test: x-pack/filebeat/input/awss3 TestBenchmarkInputS3 #30123
Comments
Pinging @elastic/integrations (Team:Integrations) |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
This looked to me like data corruption; there is some weirdness in one of the running goroutines' calls:
This is not in the crashing goroutine, but is suggestive of underlying memory corruption problems since a well behaved program should not have a pointer to a string's bytes also be a pointer to an
The lines involved are certainly suggestive of involvement. |
Yes, this would definitely explain it, both |
Flaky Test
This CI flow fired after I merged #30103, failed on the first attempt and passed when retried via the github UI "Re-run all jobs" button.
cc @kaiyan-sheng who requested I open this after me raising it on slack
Stack Trace
The text was updated successfully, but these errors were encountered: