[flakiness] Correct group for TestEndpointAgentServiceMonitoring#7165
Conversation
…ity execution group
|
💚 Build Succeeded
History
|
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
Is this supposed to be a temporary fix? We may eventually want to run these tests concurrently, in which case I think we'd want to check if the package is installed before trying to install it? |
I feel that we should first address the flakiness of how test are currently running, with the minimal blast radius (avoid adding extra flakiness) and then in a follow-up decide how these tests can be altered to support running concurrently. wdyt? 🙂 |
* fix: move TestEndpointAgentServiceMonitoring under FleetEndpointSecurity execution group * fix: specify full endpoint path in pgrep and pkill of TestEndpointMetricsAfterRestart (cherry picked from commit 31aac31)
* fix: move TestEndpointAgentServiceMonitoring under FleetEndpointSecurity execution group * fix: specify full endpoint path in pgrep and pkill of TestEndpointMetricsAfterRestart (cherry picked from commit 31aac31)
* fix: move TestEndpointAgentServiceMonitoring under FleetEndpointSecurity execution group * fix: specify full endpoint path in pgrep and pkill of TestEndpointMetricsAfterRestart (cherry picked from commit 31aac31)
* fix: move TestEndpointAgentServiceMonitoring under FleetEndpointSecurity execution group * fix: specify full endpoint path in pgrep and pkill of TestEndpointMetricsAfterRestart (cherry picked from commit 31aac31)
* fix: move TestEndpointAgentServiceMonitoring under FleetEndpointSecurity execution group * fix: specify full endpoint path in pgrep and pkill of TestEndpointMetricsAfterRestart (cherry picked from commit 31aac31)
* upstream/main: feat: bump go to 1.24.0 (elastic#6932) [CI] Fix Core DRA crossbuild (elastic#7203) fix(ci): Use correct `READ_ONLY` access value instead of `READ` (elastic#7239) ci(buildkite): add initial elastic-agent-helm-charts pipeline (elastic#7176) chore: update elastic-agent-libs to v0.18.8 (elastic#6938) [flakiness] Correct group for TestEndpointAgentServiceMonitoring (elastic#7165)





What does this PR do?
This PR relocates TestEndpointAgentServiceMonitoring to the FleetEndpointSecurity execution group to prevent test failures caused by concurrent installation attempts of the Endpoint package when tests run in different groups.
Why is it important?
Reduces flakiness of Endpoint related tests that run in our CI
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
How to test this PR locally
Related issues