kubernetes / kubernetes/perf-tests
ClusterLoader: Fix error propagation in measurements
- Dominant language
- Go
- Stars
- 989
- Forks
- 654
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 56
Description
Some errors in measurement should be logged, some cause measurement to fail and some cause test to fail.
Listed measurement should have error propagation fixed before moving test from `/test/framework` to clusterloader2:
- [ ] APIResponsiveness
- [ ] EtcdMetrics
- [ ] MetricsForE2E
- [ ] Profile
- [ ] PodStartupLatency
- [ ] ResourceUsageSummary
- [ ] SchedulingMetrics
- [ ] WaitForControlledPodsRunning
- [ ] WaitForRunningPods
Contributor guide
Research direction
Start by comparing the listed measurements in /test/framework with their clusterloader2 counterparts, focusing on how errors are currently propagated. Define the expected handling for each case—logging, failing the measurement, or failing the test—and verify all nine listed measurements before moving the test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100