-
Notifications
You must be signed in to change notification settings - Fork 127
Relax default num_workers=0 for job_clusters #4080
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
Conversation
|
Commit: 60eb642
12 interesting tests: 7 KNOWN, 3 flaky, 2 SKIP
Top 22 slowest tests (at least 2 minutes):
|
| }, | ||
| "job_clusters[0].new_cluster.num_workers": { | ||
| "action": "update", | ||
| "old": 0 |
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.
@denik Should new be null here?
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.
No, absence is expected.
It's untyped nil internally which is correctly rendered as omitted with omitempty.
|
Commit: cfbf595
20 interesting tests: 11 flaky, 7 KNOWN, 1 SKIP, 1 RECOVERED
Top 50 slowest tests (at least 2 minutes):
|
Why
Terraform only adds it if neither autoscale nor num_workers are not set. It filters it out if autoscale is set.
Tests
New acceptance test that has different configurations and asserts that requests are the same.
Difference also disappears in existing tests: in default-python recorded requests now have no difference wrt num_workers. In migrate/default-python num_workers no longer triggers drift post migration #4068