-
Notifications
You must be signed in to change notification settings - Fork 82
Run KafkaSource smokes in upgrade test #524
Run KafkaSource smokes in upgrade test #524
Conversation
85af36a
to
2fae962
Compare
Codecov Report
@@ Coverage Diff @@
## main #524 +/- ##
==========================================
- Coverage 72.87% 72.86% -0.02%
==========================================
Files 147 147
Lines 5825 5856 +31
==========================================
+ Hits 4245 4267 +22
- Misses 1335 1344 +9
Partials 245 245
Continue to review full report at Codecov.
|
//+build e2e mtsource | ||
//+build source | ||
// +build e2e | ||
// +build source mtsource |
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 think this is more correct.
It means: e2e AND (source OR mtsource)
.
Previous have meant: (e2e or mtsource) AND source
, which is weird.
@@ -315,12 +315,40 @@ function install_consolidated_channel_crds { | |||
wait_until_pods_running "${SYSTEM_NAMESPACE}" | |||
} | |||
|
|||
function install_released_consolidated_source { |
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 would remove consolidated
. Just install_released_source
.
I suppose the upgrade tests are black-box tests, in which case they can also run against the multi-tenant source variant.
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.
The function name contained consolidated
word before, that's why I didn't remove it.
That's right those tests should be a black box, but I believe future conditional logic should be in golang in installation package rather than bash scripts.
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.
My two cents: After reading install_released_consolidated_source
my first question is - what "source" ? It could be "source code". Maybe we could say install_released_event_source
instead.
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.
Looks very good! Just a few comments here and there
@@ -315,12 +315,40 @@ function install_consolidated_channel_crds { | |||
wait_until_pods_running "${SYSTEM_NAMESPACE}" | |||
} | |||
|
|||
function install_released_consolidated_source { |
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.
My two cents: After reading install_released_consolidated_source
my first question is - what "source" ? It could be "source code". Maybe we could say install_released_event_source
instead.
// well. | ||
func SourceContinualTest() pkgupgrade.BackgroundOperation { | ||
setup := func(c pkgupgrade.Context) { | ||
// TODO: not yet implemented |
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 suppose this comment is redundant? Same for the comment a few lines below
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 leave it be. The // TODO:
is reported by IDE and other dev tools. Warn log is useful on logs. That's why it's repeated.
@@ -28,3 +28,11 @@ func ChannelPostDowngradeTest() pkgupgrade.Operation { | |||
runChannelSmokeTest(c.T) | |||
}) | |||
} | |||
|
|||
// SourcePostDowngradeTest tests source operations after downgrade. | |||
func SourcePostDowngradeTest() pkgupgrade.Operation { |
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 don't know but does it make sense to rename all these functions to have the Event
prefix?
E.g. EventSourceDowngradeTest
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.
This repo contains Kafka things. KafkaSource and KafkaChannel. I'm shorting Kafka, but not only I. That naming was already in this repo before. Let's not create new names like enentsource.
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.
It looks like these two (Source and KafkaSource) are totally mixed in function names in this repo. E.g. runSourceSmokeTest vs. AssureKafkaSourceIsOperational vs. testKafkaSource vs. SourcePostDowngradeTest
That's a cosmetic thing, having just "Source" is a bit more misleading to me. Nevermind
Looks very good to me :) Leaving the merge to @mgencur |
Co-authored-by: Martin Gencur <[email protected]>
/approve |
/retest |
/lgtm |
/retest |
/woof |
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/joke |
@cardil: What concert costs only 45 cents? 50 cent featuring Nickelback. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
/test all |
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aliok The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Run KafkaSource smokes in upgrade test * Fixing unit tests * Restore upgrade tests tags * Fix codegen * Reformat README.md * Golangci Link fix * Simplify godoc SourceTestScope Conflicts fixed: * test/e2e-common.sh * test/e2e/kafka_source_test.go
* Run KafkaSource smokes in upgrade test * Fixing unit tests * Restore upgrade tests tags * Fix codegen * Reformat README.md * Golangci Link fix * Simplify godoc SourceTestScope Conflicts fixed: * test/e2e-common.sh * test/e2e/kafka_source_test.go
…tensions#524) Run KafkaSource smokes in upgrade test (knative-extensions#524) * Run KafkaSource smokes in upgrade test * Fixing unit tests * Restore upgrade tests tags * Fix codegen * Reformat README.md * Golangci Link fix * Simplify godoc SourceTestScope Conflicts fixed: * test/e2e-common.sh
* Run KafkaSource smokes in upgrade test * Fixing unit tests * Restore upgrade tests tags * Fix codegen * Reformat README.md * Golangci Link fix * Simplify godoc SourceTestScope Co-authored-by: Martin Gencur <[email protected]> Co-authored-by: Martin Gencur <[email protected]>
* Run KafkaSource smokes in upgrade test * Fixing unit tests * Restore upgrade tests tags * Fix codegen * Reformat README.md * Golangci Link fix * Simplify godoc SourceTestScope Co-authored-by: Martin Gencur <[email protected]> Co-authored-by: Martin Gencur <[email protected]> Co-authored-by: Martin Gencur <[email protected]>
…tensions#524) (#150) Run KafkaSource smokes in upgrade test (knative-extensions#524) * Run KafkaSource smokes in upgrade test * Fixing unit tests * Restore upgrade tests tags * Fix codegen * Reformat README.md * Golangci Link fix * Simplify godoc SourceTestScope Conflicts fixed: * test/e2e-common.sh
Partially resolves #67
Proposed Changes
KafkaSource
on upgrade testsContinual tests will follow to fully resolve #67