knative / knative/eventing

[flaky] test/rekt.TestInMemoryChannelTLS/SubscriptionTLSWithAdditionalTrustBundle/Requirement/channel_is_ready

Open
#9,391 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auto:flaky
Dominant language
Go
Stars
1.6k
Forks
631
Avg merge
3d 13h
Merged PRs (30d)
6

Description

Auto-generated issue tracking flakiness of test
  • Test name: test/rekt.TestInMemoryChannelTLS/SubscriptionTLSWithAdditionalTrustBundle/Requirement/channel_is_ready
  • Repository name: eventing

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating test/rekt.TestInMemoryChannelTLS/SubscriptionTLSWithAdditionalTrustBundle/Requirement/channel_is_ready in the eventing repository and run it repeatedly to observe the flakiness. Trace the failing setup and test output to identify the cause; done means the named test runs reliably without intermittent failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.