-
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]: TestOtelFileProcessing – there should be exported logs by now #4617
Comments
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
probably valid error, setup changed a bit with update to 0.99 |
One more failure on |
related to this issue here: open-telemetry/opentelemetry-collector#10031 |
Are we sure this test is failing due to open-telemetry/opentelemetry-collector#10031? I just built Agent from
|
it works locally on my end as well. my take on this is that machines on CIs are slower and it takes a bit of time to release bound port. in the meantime another process is starting. we've seen something like this before. it started appearing just after i upgraded versions from 97 i also needed to change check for validate because in version 0.97 for valid config output is empty. for 97+ it shows these 3 lines you shared as well |
Thanks, I was also thinking it must be something along these lines, unfortunately 😞. Given that, it would be tempting to add a bit of a sleep or something in the test between the two |
Failing test case
TestOtelFileProcessing
Error message
there should be exported logs by now
Build
https://buildkite.com/elastic/elastic-agent/builds/8506#018f0d68-b5e4-46e6-93a8-91612f46c4e8
OS
Linux
Stacktrace and notes
The text was updated successfully, but these errors were encountered: