stat test is flakey
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
### What is the issue?
Timed out in `external_prometheus_deep` suite with the following error:
```
Error: TestCliStatForLinkerdNamespace - timed-out checking stats (20s)
--- FAIL: TestCliStatForLinkerdNamespace (36.05s)
--- FAIL: TestCliStatForLinkerdNamespace/linkerd_viz_stat_svc_-n_linkerd-stat-test (20.33s)
stat_test.go:269: Error stripping header and trailing newline; full output:
```
https://github.com/linkerd/linkerd2/runs/4887651353?check_suite_focus=true
**Edit**: seen again
https://github.com/linkerd/linkerd2/runs/4954477559?check_suite_focus=true
### How can it be reproduced?
Bad luck :( N/A
### Logs, error output, etc
N/A
### output of `linkerd check -o short`
N/A
### Environment
N/A
### Possible solution
_No response_
### Additional context
_No response_
### Would you like to work on fixing this bug?
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the external_prometheus_deep suite and the failure at stat_test.go:269, then inspect the linked GitHub Actions runs for the full output and timing. Determine why TestCliStatForLinkerdNamespace can exceed the 20-second check and verify that the stat test passes reliably without the timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, prometheus
- Domain
- cli, observability, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100