knative / knative/eventing

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

Open
#9,389 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_has_HTTPS_address
  • 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 with test/rekt.TestInMemoryChannelTLS/SubscriptionTLSWithAdditionalTrustBundle/Requirement/Channel_has_HTTPS_address and run the named test repeatedly to confirm the flakiness. Trace the test's TLS and channel-address setup, then define done as a consistently passing test run without changing the stated HTTPS requirement.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.