-
Notifications
You must be signed in to change notification settings - Fork 143
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]: Multiple tests – failed to fetched test output at ... #4279
Comments
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
I see it's passed after 2 retries. Shouldn't we add retries to |
@pazone we can, but I think we should also identify why the connection to hosts was unreliable, it happened twice again in https://buildkite.com/elastic/elastic-agent/builds/7264#018dc323-a3fd-423d-bed4-75fcf4027ffc Looks like the issue occurs periodically and lasts for a few hours. |
I think we add retries here regardless in case it improves the situation. It also looks like we drop the underlying error from |
If we can catch this while the VM is still alive we can check what the instance is doing in GCP. |
Closing in favor of #4356 |
Failing test case
It's not a test case, the error happens after tests finished
Error message
Failed for instance windows-amd64-2022-fleet (@ 35.232.65.142): failed to execute tests on instance ogc-windows-amd64-2022-fleet-2486: error running sudo tests: failed to fetched test output at %home%\agent\build\TEST-go-remote-windows-amd64-2022-fleet-sudo.integration.out
Build
https://buildkite.com/elastic/elastic-agent/builds/7261#018dc1f1-d326-455c-bd41-fcad4fa2e0af
OS
Linux, Mac, Windows
Stacktrace and notes
>> (windows-amd64-2022-fleet) Failed for instance windows-amd64-2022-fleet (@ 35.232.65.142): failed to execute tests on instance ogc-windows-amd64-2022-fleet-2486: error running sudo tests: failed to fetched test output at %home%\agent\build\TEST-go-remote-windows-amd64-2022-fleet-sudo.integration.out
Looks like the SSH session stopped working since this code is failing:
elastic-agent/pkg/testing/runner/windows.go
Lines 311 to 322 in f23c279
The text was updated successfully, but these errors were encountered: