This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
e2e: test flake during metrics testing
At least once the "direct-testing-metrics data full" test failed with: Dec 15 22:36:03.221: Timed out after 10.005s. Expected <string>: have pod IP Expected <string>: not to be empty GET failed Unexpected error: <*url.Error | 0xc000cb0e70>: { Op: "Get", URL: "http://default.format-node-hcz2c:10010/metrics", Err: <*errors.errorString | 0xc0015c9800>{ s: "dialer failed: unable to upgrade connection: pod not found (\"format-node-hcz2c_default\")", }, } Get "http://default.format-node-hcz2c:10010/metrics": dialer failed: unable to upgrade connection: pod not found ("format-node-hcz2c_default") occurred to be empty Better assertion annotations are necessary to understand which pod these assertions are about. If this was a pod that just began starting, then the 10s timeout may have been too short.
- Loading branch information