[flaky] test/rekt.TestTriggerTLSSubscriber/Trigger_with_TLS_subscriber_-_trust_bundle/Requirement/Wait_for_failing_Trigger_to_become_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.TestTriggerTLSSubscriber/Trigger_with_TLS_subscriber_-_trust_bundle/Requirement/Wait_for_failing_Trigger_to_become_ready
* **Repository name**: eventing
Contributor guide
Research direction
Start by running test/rekt.TestTriggerTLSSubscriber/Trigger_with_TLS_subscriber_-_trust_bundle/Requirement/Wait_for_failing_Trigger_to_become_ready and capture how it becomes flaky. Trace the test's readiness wait and TLS trust-bundle setup, then confirm the test passes reliably before considering the issue done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100