Skip to content
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

[YUNIKORN-2135] Add integration test code coverage #164

Closed
wants to merge 1 commit into from

Conversation

FrankYang0529
Copy link
Member

What is this PR for?

Add a new value enableGoCoverDir. If the value is true, we add an output folder and set GOCOVERDIR for yunikorn deployment.

What type of PR is it?

  • - Improvement

What is the Jira issue?

https://issues.apache.org/jira/browse/YUNIKORN-2135

Comment on lines +115 to +120
volumes:
- name: go-cover-dir
hostPath:
path: /go-cover-dir/
type: DirectoryOrCreate
{{- end }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If follow this approach, I believe we'll need extra code somewhere which fetches the results from the Docker containers if we want to automate this, correct? Because we won't have it right away on the host filesystem. I guess we need a docker cp somewhere.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@pbacsko pbacsko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 looks good. Internally we'll need PVC support other than HostPath but I believe it's good for a start.

cc @wilfred-s

Copy link
Contributor

@craigcondit craigcondit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm -1 on this. I am really not a fan of polluting our helm charts with additional cruft that is completely useless for end users. This is just going to lead to confusion. If we're going to do this as part of e2e testing fine; there needs to be a way to dynamically add this from within the k8shim repo, not in the primary helm charts used here in yunikorn-release.

@FrankYang0529 FrankYang0529 deleted the YUNIKORN-2135 branch February 26, 2024 13:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants