-
Notifications
You must be signed in to change notification settings - Fork 159
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
[STRMCMP-1639] Integration Test Fix #277
Conversation
integ/README.md
Outdated
8. Set the following for the Go test: | ||
Package path: github.com/lyft/flinkk8soperator/integ | ||
Env: INTEGRATION=true;OPERATOR_IMAGE=flinkk8soperator:local;RUN_DIRECT=true | ||
Program Args: -timeout 40m -check.vv IntegTest |
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 thought IntegTest
is not needed.
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 removed this when attempting to target a single test. No luck there for now so leaving as is since this is what was there for the integration test prior. In the future we'll figure out how to target a single test as I'll likely write an integration test for fallback without savepoint
integ/README.md
Outdated
is non-trivial due to cgroup configurations. Instead, we will use a version | ||
that is compatible with v1beta1 CRD's which corresponds to <1.22. CRD's v1 | ||
is only available with client >=1.16, however, the client used here is 1.14 | ||
and the upgrade is non-trivial. |
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.
Maybe just add a TODO here with the jira to upgrade client?
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.
Created a ticket for the 1.22 upgrade and added
failingJobTest(s, c, "taskfailure", func() { | ||
f, err := os.OpenFile(s.Util.CheckpointDir+"/fail", os.O_RDONLY|os.O_CREATE, 0666) | ||
err := s.Util.ExecuteCommand("minikube", "ssh", "touch /tmp/checkpoints/fail && chmod 0644 /tmp/checkpoints/fail") |
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 get this test, you're creating and modifying privs on a file and then just asserting the commands ran without errors?
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.
Changes the behavior of the flink app: https://github.com/lyft/flinkk8soperator/blob/master/integ/operator-test-app/src/main/java/com/lyft/OperatorTestApp.java#L92
@@ -163,7 +166,7 @@ func (s *IntegSuite) TestCancelledJobWithoutSavepoint(c *C) { | |||
c.Assert(err, IsNil) | |||
|
|||
// wait a bit | |||
time.Sleep(1 * time.Second) | |||
time.Sleep(5 * time.Second) |
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.
Don't have to change anything but generally speaking I am never a fan of such sleep timers in tests (just makes it flakey).
I would always promote to change this to an polling method with exponential delay (and an exit criteria). Again, don't need to do that now but just wanted to point it out.
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.
Agreed. Will leave as a future update or at least keep in mind while writing future integration tests for this repo
integ/scaleup_test.go
Outdated
log.Info("All pods torn down") | ||
} | ||
// TODO: https://github.com/lyft/flinkk8soperator/issues/278 | ||
//func (s *IntegSuite) TestInPlaceScaleUp(c *C) { |
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.
Instead of commenting all this out I believe you can just do
c.Skip("Skipping because of blah")
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.
added! Didn't know this existed! Thx!
Tons of thanks for tackling down complicated problem! |
1db3074
/PTAL @leoluoInSea |
overview
Integrations tests working in CI again
Additional Info