You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you expect to happen instead?
That it would display the results, but it does not. You see the command being run, but no results displayed in the terminal.
How can we reproduce the bug? (as minimally and precisely as possible)
It isn't a "problem" unique to pytest or coverage, but getting most types of feedback from the container in the terminal. The easiest way to reproduce it is any of the following:
dev:
sync:
...
onUpload:
exec:
- command: ls
# or
onUpload:
exec:
- command: bash -c "ls"
# or
onUpload:
exec:
- command: kubectl exec -it pod-0 -- ls
local: true
# or
onUpload:
exec:
- command: kubectl exec -it pod-0 -- bash -c "ls"
local: true
In each case you'll see the command being run, but not the results:
you should be able to see the output in the devspace logs afaik, e,g. in one of the files in $CWD/.devspace/logs. Atleast that was the case last time I've used onUpload functionality.
Im not aware of an option that the output is printed to the terminal
What happened?
Trying to run
pytest
andcoverage
, and display the results in terminal usingonUpload.exec.command
.This is probably just user error. I've asked about it on SO.
What did you expect to happen instead?
That it would display the results, but it does not. You see the command being run, but no results displayed in the terminal.
How can we reproduce the bug? (as minimally and precisely as possible)
It isn't a "problem" unique to
pytest
orcoverage
, but getting most types of feedback from the container in the terminal. The easiest way to reproduce it is any of the following:In each case you'll see the command being run, but not the results:
My devspace.yaml:
Local Environment:
Kubernetes Cluster:
docker-desktop
Anything else we need to know?
That should cover it. More than likely something I'm doing wrong.
The text was updated successfully, but these errors were encountered: