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

Don't extract e2e.test and ginkgo binary into artifacts.BaseDir() #97

Closed
mkumatag opened this issue Mar 1, 2021 · 5 comments
Closed
Labels
sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@mkumatag
Copy link
Member

mkumatag commented Mar 1, 2021

These two binaries are extracted under the Artifacts folder and collected post-run and this end up utilizing a lot of space in the GCS which is not required as nothing else is captured, hence it will be good if we can put them into some temp folder and trigger from there

@mkumatag
Copy link
Member Author

mkumatag commented Mar 1, 2021

location:

t.e2eTestPath = filepath.Join(artifacts.BaseDir(), "e2e.test")
t.ginkgoPath = filepath.Join(artifacts.BaseDir(), "ginkgo")

@amwat
Copy link
Contributor

amwat commented Mar 1, 2021

I could see both sides here, it might be useful for someone while debugging to know exactly what binary was used.
But agree that it should be intentional, and configurable.

In general, we want to add a way where deployer/testers can choose to distinguish the artifacts used during the run vs the artifacts that the deployer/tests want to upload.

@mkumatag
Copy link
Member Author

mkumatag commented Mar 2, 2021

I could see both sides here, it might be useful for someone while debugging to know exactly what binary was used.
But agree that it should be intentional, and configurable.

In general, we want to add a way where deployer/testers can choose to distinguish the artifacts used during the run vs the artifacts that the deployer/tests want to upload.

Agree for somecase it will be helpful to collect as artifacts but in case of downloading or using these binaries from some other repository is very costly, not everyone can afford that default feature. As you mentioned let's think about putting it somewhere else so that artifact does not collect it.

@amwat
Copy link
Contributor

amwat commented Mar 19, 2021

This is fairly similar to #98 let's track it there.

Once that is fixed, default would be RunDir() (so no upload) and we can add functionality to allow optionally uploading (by copying them back to artifacts.BaseDir())

/cc @justinsb

/close

@k8s-ci-robot
Copy link
Contributor

@amwat: Closing this issue.

In response to this:

This is fairly similar to #98 let's track it there.

Once that is fixed, default would be RunDir() (so no upload) and we can add functionality to allow optionally uploading (by copying them back to artifacts.BaseDir())

/cc @justinsb

/close

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.

sig-testing issues (kubernetes-sigs) automation moved this from To Triage to Done Mar 19, 2021
@spiffxp spiffxp added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Development

No branches or pull requests

4 participants