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

debug test log shows #3609

Open
yupor5 opened this issue Nov 21, 2024 · 1 comment
Open

debug test log shows #3609

yupor5 opened this issue Nov 21, 2024 · 1 comment
Milestone

Comments

@yupor5
Copy link

yupor5 commented Nov 21, 2024

Type: Bug

When debugging test scheduling, the log shows that the query is not clear enough. The log shows merged queries, and the - v operation cannot be found. Why can't debug test include - v

Extension version: 0.42.1
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info
Item Value
CPUs 12th Gen Intel(R) Core(TM) i5-12400 (12 x 2496)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 31.78GB (12.68GB free)
Process Argv E:\golang\source8\matapi --crash-reporter-id accb328f-e77e-41b5-beb8-ef12c42b9970
Screen Reader no
VM 50%
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
da93g388:31013173
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31185842
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

@gopherbot gopherbot added this to the Untriaged milestone Nov 21, 2024
@firelizzard18
Copy link
Contributor

Are you running via a code lens or via the play button/test explorer? What do you expect to be happening? What do you mean by "test scheduling"?

If you are running via the play button/test explorer, that uses go test -json which internally is treated as -v (specifically, -test.v=test2json). go test -v -json is redundant, and is also buggy.

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

No branches or pull requests

3 participants