[flaky] test/rekt.TestSinkBindingV1Deployment_BrokerAsSinkTLS/SinkBinding_V1_Deployment_BrokerAsSink_test/Requirement/Broker_has_HTTPS_address
Open
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.TestSinkBindingV1Deployment_BrokerAsSinkTLS/SinkBinding_V1_Deployment_BrokerAsSink_test/Requirement/Broker_has_HTTPS_address
- Repository name: eventing
Contributor 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.
Research direction
Start by locating and running test/rekt.TestSinkBindingV1Deployment_BrokerAsSinkTLS/SinkBinding_V1_Deployment_BrokerAsSink_test/Requirement/Broker_has_HTTPS_address in the eventing repository. Investigate why the broker HTTPS-address assertion is flaky, then make the test reliable and verify it passes consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100