[flaky] test/e2e/multicontainerprobing.TestMultiContainerProbeStartFailingAfterReady

Open
#16,788 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go, kubernetes
Domain
backend, testing

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:flaky
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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from knative/serving

All issues in knative/serving

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.