if testcase for a long time,the test source manager will not update status

[ministorck]

Type: Bug

Behaviour

Expected vs. Actual

the test case status can update in normal.

Steps to reproduce:

1. i have something for test, their is some case have to use long time. (ex:2 seconds)
2. start from this case ,the source manager table can not update case status.
3. before this case,the case can update status on the test source manager table,

Diagnostic data

• Python version (& distribution if applicable, e.g. Anaconda): 3.8.10
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
• Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

User Settings

languageServer: "Pylance"

testing
• pytestArgs: "<placeholder>"
• pytestEnabled: true

Extension version: 2024.0.1
VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:41:37.860Z)
OS version: Linux x64 5.15.0-92-generic
Modes:

System Info

Item	Value
CPUs	AMD Ryzen 7 PRO 7730U with Radeon Graphics (16 x 1600)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off 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: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off
Load (avg)	1, 1, 3
Memory (System)	14.42GB (5.32GB free)
Process Argv	--unity-launch --crash-reporter-id ccf06ee0-64a7-44de-b7f0-28e767ad415d
Screen Reader	no
VM	0%
DESKTOP_SESSION	ubuntu
XDG_CURRENT_DESKTOP	Unity
XDG_SESSION_DESKTOP	ubuntu
XDG_SESSION_TYPE	x11

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:30962250
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
pydisww1:30959800
edj9j583:30958191
fegfb526:30961430
7j2b6412:30967274
bg6jg535:30958357

[eleanorjboyd]

Hi! Could you upload a video or something so I can see the status you are discussing? Or before and after screenshots if the video will be too large. Can you also include your logs with trace logs on, you can do so by setting your log level to trace via theDeveloper: set log level command in the command palette then getting the logs from the python output channel.

[eleanorjboyd]

Hello! I am closing this issue since we have not heard back on the above question, please comment with the requested information if you are still experiencing this problem and I can re-open it. Thanks