[flaky] test/e2e/multicontainerprobing.TestMultiContainerProbeStartFailingAfterReady
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start with test/e2e/multicontainerprobing.TestMultiContainerProbeStartFailingAfterReady and inspect its recent failures to identify the flaky behavior. Read the test setup and related multi-container probe tests, then reproduce the failure with the focused end-to-end test. Done means the test reliably passes while still checking the intended probe behavior.
Written by the indexing model from the issue text.
Description
Auto-generated issue tracking flakiness of test
- Test name: test/e2e/multicontainerprobing.TestMultiContainerProbeStartFailingAfterReady
- Repository name: serving
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 1.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 51
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from knative/serving
-
progress-deadline annotation accepts "0s" although validation says it must be positivePossibly taken @BahaaMattar claimed this today. Openarea/API kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
envFrom validation errors have no entry index, and their paths are garbled when several entries are invalidPossibly taken @BahaaMattar claimed this today. Openarea/API kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
auto:flaky
Difficulty 4/5 3-5 days Newbie friendliness 35/100
knative/serving#16789 · 1 comment ·
Maintainers usually reply within 1 day
-
auto:flaky
Difficulty 4/5 3-5 days Newbie friendliness 25/100
knative/serving#16787 · 1 comment ·
Maintainers usually reply within 1 day
-
area/API area/autoscale kind/feature
Difficulty 5/5 Over a week Newbie friendliness 38/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
api cleanup
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
router-for-me/CLIProxyAPI#7708 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100