-
Notifications
You must be signed in to change notification settings - Fork 160
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]: TestFakeInputSuite/TestManager_OutputChange – Should be true #4286
Comments
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
The following is my analysis: This test aims that once a component model is running, upon receiving a new component model, which replaces a component, the component from the 1st model is stopped before the new component starts. In other words:
The manager starts with '1st config' then receives '2nd config'. Once it receives '2nd config', The test failed because from the test's perspective When updating the component model, In addition to that, even thought the test receives state changes for both components in the same goroutine, it isn't guaranteed it'll always read first the state of the 1st component then the state of the second. Given all the above I conclude it's expected, and not a failure for the test, to see the state changes out of order. It's better to check all the necessary transitions happened. That means, using the example from the beginning, |
The analysis of what is happening is great, but this suggestion defeats the purpose of the test, which is a regression test for a bug that caused real problems. We do need to verify that component A and component B are started and stopped in the correct order. The original change was #2226 which is linked back to a support case with a failed upgrade because we attempted to start a second instance of endpoint before the first one had actually stopped. We need to maintain this property of the system. |
Failing test case
TestFakeInputSuite/TestManager_OutputChange
Error message
Should be true
Build
https://buildkite.com/elastic/elastic-agent/builds/7268#018dc3d2-0f4b-42c2-bf41-1274db4e77e9
OS
Windows
Stacktrace and notes
The text was updated successfully, but these errors were encountered: