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
{{ message }}
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
I've read the documentation on the wiki, which fails to document anything about"output": "/path/to/my/output/binary", which from my testing, applies only to "mode": "debug" and not "mode": "test".
...
Using GOPATH: /path/to/repo/.go
Current working directory: /path/to/repo/mypackage
Running: /path/to/dlv test --headless=true --listen=127.0.0.1:16482 --api-version=2 --log=true -- -test.run TestMyFunction
...
...
Using GOPATH: /path/to/repo/.go
Current working directory: /path/to/repo
Running: /path/to/dlv debug --headless=true --listen=127.0.0.1:3791 --api-version=2 --log=true --output=/path/to/repo/bin/debug --
...
You see in the trace of "mode": "debug" that there is an expected --output /path/to/bin/debug whereas in "mode": "test", there is no expected --output /path/to/bin/debug.test.
This might not be a big issue for most since the in typical Go workflow as explained in #1345, debug / test creates a binary next to the file being tested. However, the fact that the dlv test so explicitly supports it, would mean it's a definitely a feature to be missed.
Version
0.9.2
The text was updated successfully, but these errors were encountered:
I've read the documentation on the wiki, which fails to document anything about
"output": "/path/to/my/output/binary"
, which from my testing, applies only to"mode": "debug"
and not"mode": "test"
."mode": "test"
launch.json
Trace:
"mode": "debug"
launch.json
Trace:
You see in the trace of
"mode": "debug"
that there is an expected--output /path/to/bin/debug
whereas in"mode": "test"
, there is no expected--output /path/to/bin/debug.test
.This might not be a big issue for most since the in typical Go workflow as explained in #1345, debug / test creates a binary next to the file being tested. However, the fact that the
dlv test
so explicitly supports it, would mean it's a definitely a feature to be missed.Version
0.9.2
The text was updated successfully, but these errors were encountered: