-
Notifications
You must be signed in to change notification settings - Fork 19
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
📝 Parallelize the Config Policy controller E2E tests #145
📝 Parallelize the Config Policy controller E2E tests #145
Conversation
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 good overall! Just a few small questions. I'd also prefer to see a more descriptive commit message.
Makefile
Outdated
$(GINKGO) -v -p --fail-fast -procs=7 $(E2E_TEST_ARGS) test/e2e | ||
# |
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.
Do we need to specify -procs
here? From the docs, it sounds like it would pick an "ideal" number based on the machine it's running on. Since this same target will run in both the github action run and locally, I feel like it could be better to let it choose.
Also, is there an accidental empty comment 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.
cuz our CI default is 2
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 wonder limitation looks more procs faster also I didn't request a review because I am not finished yet so weird.. I cannot even remove you from the reviewer list. you are the default reviewer now
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 wonder limitation looks more procs faster also I didn't request a review because I am not finished yet so weird.. I cannot even remove you from the reviewer list. you are the default reviewer now
FYI for next time, if you open a Draft PR, it doesn't get assigned reviewers but I think workflows still run. 🙂
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.
oh!! Draft PR I will ask you next time Thanks for letting know good info!!! @dhaiducek
@@ -11,7 +11,7 @@ spec: | |||
- complianceType: musthave | |||
objectDefinition: | |||
apiVersion: v1 | |||
kind: ConfigMap | |||
kind: case28-ConfigMap |
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.
What is this change for? It seems like the test just needs any policy (it doesn't care if it's compliant or not) but this seems odd.
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.
good catch!!
@@ -24,8 +24,8 @@ const ( | |||
tlsProfileInformYaml string = "../resources/case11_apiserver_config/tls_profile_inform.yaml" | |||
) | |||
|
|||
var _ = Describe("Test APIServer Config policy", func() { | |||
Describe("Test etcd encryption and tls profile", func() { | |||
var _ = Describe("Test APIServer Config policy", Serial, func() { |
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 test is removing API so affect others
Makefile
Outdated
@@ -205,7 +205,7 @@ install-resources: | |||
|
|||
.PHONY: e2e-test | |||
e2e-test: e2e-dependencies | |||
$(GINKGO) -v --fail-fast $(E2E_TEST_ARGS) test/e2e | |||
$(GINKGO) -v -p -procs=7 --fail-fast $(E2E_TEST_ARGS) test/e2e |
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.
CI default is 2 so I had to do this
deleteConfigPolicies([]string{case13Unterminated, case13WrongArgs}) | ||
}) | ||
}) | ||
// Though the Bugzilla bug #2007575 references a different incorrect behavior, it's the same | ||
// underlying bug and this behavior is easier to test. | ||
Describe("RHBZ#2007575: Test that the template updates when a referenced resource object is updated", func() { | ||
const configMapName = "configmap-update-referenced-object" |
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 just added Describe around describe
21a8601
to
e2e72bb
Compare
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.
Thanks! This is going to be so great to not have to wait an hour for the E2E tests! I have some comments/questions.
d376659
to
a205045
Compare
test/resources/case20_delete_objects/case20_change_config_policy.yaml
Outdated
Show resolved
Hide resolved
4c89fbf
to
84a5b3e
Compare
test/resources/case20_delete_objects/case20_change_config_policy_not_prune.yaml
Outdated
Show resolved
Hide resolved
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.
Just one minor comment but otherwise, this looks great to me! Nice job.
8de8560
to
c21f11e
Compare
c21f11e
to
0b7955c
Compare
@yiraeChristineKim could you please squash the commits? |
79b28d9
to
df14335
Compare
Signed-off-by: Yi Rae Kim <yikim@redhat.com>
df14335
to
5278607
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mprahl, yiraeChristineKim 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 |
The Config Policy controller's E2E tests in its repo takes roughly 45 minutes to run. This is due to all the test running serially. These could be optimized to run in parallel for faster execution.
Acceptance Criteria:
The config-policy-controller E2E tests run in under 20 minutes or Christine declares it impossible.