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
Running the SourceOpsMapParTest tests from Ox never finishes. There's an endlessly spinning wheel:
In the debug console, I can see that the tests have finished:
===============================================
Total duration: 9.63s
All 1 test suites passed.
===============================================
Stopping the tests does nothing (using the square button on the right in the "test results" window). Sometimes this happens on the first test run, sometimes the first completes successfully, and only the second fails.
Moreover, quitting VS Code (which I'm using as the metals host) doesn't kill the Metals-started bloop.Server process. I have to manually kill it after I exit VS Code (which shuts down cleanly)
Expected behavior
the tests are nicely reported in the "test results" window, or at least - not hang.
existing VS Code cleans up any processes that have been started
Operating system
macOS
Editor/Extension
VS Code
Version of Metals
1.3.5
Extra context or search terms
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Running the
SourceOpsMapParTest
tests from Ox never finishes. There's an endlessly spinning wheel:In the debug console, I can see that the tests have finished:
Stopping the tests does nothing (using the square button on the right in the "test results" window). Sometimes this happens on the first test run, sometimes the first completes successfully, and only the second fails.
Moreover, quitting VS Code (which I'm using as the metals host) doesn't kill the Metals-started
bloop.Server
process. I have to manually kill it after I exit VS Code (which shuts down cleanly)Expected behavior
Operating system
macOS
Editor/Extension
VS Code
Version of Metals
1.3.5
Extra context or search terms
No response
The text was updated successfully, but these errors were encountered: