-
Notifications
You must be signed in to change notification settings - Fork 273
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
Manually running tests in interactive mode does not generate test artifacts #1475
Comments
This issue has been automatically marked as stale because it hasn't had any activity in 60 days. It will be closed in 14 days if no further activity occurs (e.g. changing labels, comments, commits, etc.). Please feel free to remove the label if you think it doesn't apply. Thank you for submitting this issue and helping make Garden a better product! |
This issue has been automatically marked as stale because it hasn't had any activity in 60 days. It will be closed in 14 days if no further activity occurs (e.g. changing labels, comments, commits, etc.). Please feel free to tag a maintainer and ask them to remove the label if you think it doesn't apply. Thank you for submitting this issue and helping make Garden a better product! |
Closing as a duplicate of #1739 |
Bug
Current Behavior
When running garden tests in interactive mode (the default when using
garden run test
), the artifacts do not generate. Running tests with the interactive flag set to false (--interactive=false
) allows the artifacts to generate.Expected behavior
Artifacts should generate as defined whether or not
garden run test
is run with--interactive=false
or--interactive=true
Reproducible example
Run defined garden tests manually using
garden run test <module> <test-name>
. Check your defined area in.garden/artifacts
to find that no artifacts were generated.Run defined garden tests manually using
garden run test <module> <test-name> --interactive=false
. Check your defined area in.garden/artifacts
to find that the artifacts were generated this time.Workaround
When manually running tests, use
--interactive=false
.Suggested solution(s)
I personally think that artifacts should generate regardless of the
--interactive
flag status.Your environment
garden version
0.10.16
kubectl version
docker version
Docker version 19.03.5, build 633a0ea
The text was updated successfully, but these errors were encountered: