-
Notifications
You must be signed in to change notification settings - Fork 148
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
[Flaky Test]: TestUpgradeBrokenPackageVersion – unexpected fault address #5231
Comments
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
Here's the stack trace in that last line parsed out into a readable format: |
Here's the most relevant section:
|
It seems like the goroutine triggering the It's not immediately clear that it's doing anything wrong since the offending function is in the net/http package but I'm going to ping @elastic/apm-agent-go anyway on the chance they may have seen this before. |
go agent v1 is ancient. Aren't we using v2 in elastic agent or am I missing something ? 🤔 |
I don't recall having seen that panic with the agent before. I'm also a bit confused by the above; I only see /v2 libraries in go.mod, and |
Took a quick look, and it seems that the PR to upgrade apm agent to v2 was merged 3 weeks ago (#4939), so Could there be something weird going on with the Elastic Agent upgrading from
|
Yes, two things:
So go agent v1 will eventually age out of our tests but that will happen as minor releases happen. I don't think we need any deeper investigation unless this starts happening a lot, and if it is a rare problem related to go agent v1 it will age out eventually. |
Failing test case
TestUpgradeBrokenPackageVersion
Error message
unexpected fault address
Build
https://buildkite.com/elastic/elastic-agent-extended-testing/builds/1663
OS
Windows
Stacktrace and notes
The text was updated successfully, but these errors were encountered: