[flaky] test/rekt.TestInMemoryChannelTLS/SubscriptionTLSWithAdditionalTrustBundle/Requirement/subscription_dead_letter_is_ready
Open
auto:flaky
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 631
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 6
Description
### Auto-generated issue tracking flakiness of test
* **Test name**: test/rekt.TestInMemoryChannelTLS/SubscriptionTLSWithAdditionalTrustBundle/Requirement/subscription_dead_letter_is_ready
* **Repository name**: eventing
Contributor guide
Research direction
Start by running test/rekt.TestInMemoryChannelTLS/SubscriptionTLSWithAdditionalTrustBundle/Requirement/subscription_dead_letter_is_ready and capturing the intermittent failure output. Read the surrounding rekt test and its TLS or subscription setup to identify the nondeterministic behavior; done means the test passes reliably without masking the underlying requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100