Flaky TestGetFullStateHandler

[github-actions]

TestGetFullStateHandler

pkg/alertmanager/alertmanager_test.go

About This Issue

This issue tracks a flaky test that has been detected failing inconsistently. Each week our analysis tool runs and detects this test as flaky, it will add a comment below with recent failure data and who might be able to help.

🔍 How to investigate

1. Run it locally to see if you can reproduce: go test -count=10000 -run TestGetFullStateHandler ./...
2. Check the failure logs in the comments below - they might show a pattern
3. Look for timing issues - race conditions, timeouts, or external dependencies
4. Review recent changes - check commits that modified this test or the code under test recently

🎯 Next steps

• Can you fix it? Great! That would help the whole team
• Need help? Ask someone who has worked on this area recently
• Can't fix it right now? Consider adding logs and metrics so that next time it's easier to debug.
• Obsolete test? Maybe it's time to remove it or skip it with t.Skip()

This test has been identified as flaky by go-flaky-tests.

[github-actions]

Hey there! This test is still being flaky

This test failed 52 times across 4 different branches in the last 7d.

Who might know about this?

• @santihernandezc - made a relevant commit on 2025-07-14: 90b2873 "Alertmanager: Add an endpoint to get the full state (Alertmanager: Add an endpoint to get the full state #12014)"

If any of you have a few minutes, could you take a look? You might have context on what could be causing the flakiness.

Recent failures

• Failed run - test (3, 4) (Attempt #⁠1)
• Failed run - test (3, 4) (Attempt #⁠1)
• Failed run - test (3, 4) (Attempt #⁠1)

💡 Check the issue description above for investigation tips and next steps!

Thanks for helping keep our tests reliable!