-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GH actions - E2E tests for namespaced broker #2450
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
@@ -27,8 +27,22 @@ if [ "${EVENTING_KAFKA_BROKER_CHANNEL_AUTH_SCENARIO:-""}" != "" ]; then | |||||||||
success | ||||||||||
fi | ||||||||||
|
||||||||||
# TODO: going to be reverted once we have the Prow changes in https://github.com/knative/test-infra | ||||||||||
export BROKER_CLASS="Kafka" | ||||||||||
Comment on lines
+30
to
31
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still hardcoded in Prow jobs. Gonna pass this once knative/test-infra#3466 is merged. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
what about this option? that would facilitate running them locally without specifying the class since it would default to the existing/stable one. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I personally always prefer explicit errors over invisible defaulting. However, I am ok with that if you feel strong about it There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The job is there, can we fix the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
This is a bad comment of mine, sorry. I want to make sure that I am not breaking any E2E tests for the regular KafkaBroker with this PR. So, I will remove that TODO in a separate PR when I am 100% sure that E2E tests are passing in both class. |
||||||||||
|
||||||||||
if [[ -z "${BROKER_CLASS}" ]]; then | ||||||||||
fail_test "Broker class is not defined. Specify it with 'BROKER_CLASS' env var." | ||||||||||
else | ||||||||||
echo "BROKER_CLASS is set to '${BROKER_CLASS}'. Running tests for that broker class." | ||||||||||
fi | ||||||||||
|
||||||||||
if [ "${BROKER_CLASS}" == "KafkaNamespaced" ]; then | ||||||||||
# if flag exists, only test tests that are relevant to namespaced KafkaBroker | ||||||||||
echo "BROKER_CLASS is set to 'KafkaNamespaced'. Only running the relevant tests." | ||||||||||
go_test_e2e -timeout=1h ./test/e2e_broker/... || fail_test "E2E suite failed (directory: ./e2e_broker/...)" | ||||||||||
success | ||||||||||
fi | ||||||||||
|
||||||||||
go_test_e2e -timeout=1h ./test/e2e/... || fail_test "E2E suite failed (directory: ./e2e/...)" | ||||||||||
go_test_e2e -timeout=1h ./test/e2e_broker/... || fail_test "E2E suite failed (directory: ./e2e_broker/...)" | ||||||||||
go_test_e2e -timeout=1h ./test/e2e_sink/... || fail_test "E2E suite failed (directory: ./e2e_sink/...)" | ||||||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're enabling these controllers which means that they will be released but I think we should solve the known issues first like:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/hold
OK we need to make a decision:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer solving known issues because right now these deployments aren't debuggable at all, no tracing, no logging config or stale ConfigMaps contain buggy behavior (consumer and producer configs)