tests are not configured after reloading the window

[meganrogge]

Testing #22081

I was running tests, reloaded the window, tests are no longer discovered.

[meganrogge]

output:

python /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12691017/pythonFiles/unittestadapter/discovery.py --port 49541 --uuid cc45b0be-38c9-400e-a3ba-9772b4b8fe74 --udiscovery -v -s . -p *test*.py
python /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12691017/pythonFiles/unittestadapter/discovery.py --port 49541 --uuid b7dfe702-01c0-4972-a117-08c1a25612da --udiscovery -v -s . -p *test*.py
python /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12691017/pythonFiles/unittestadapter/discovery.py --port 49541 --uuid e2f17684-6abc-4e2c-9970-a6f07825ff5c --udiscovery -v -s . -p *test*.py

[meganrogge]

ined
2023-09-26 11:39:37.845 [debug] Cached data exists KeyPrefix=Cache_Method_Output_b._selectIfLaunchedViaActivatedEnv-Args=true
2023-09-26 11:39:37.846 [debug] Clearing context for python dependencies not installed: /Users/meganrogge/Repos/inc_dec_example_repo/inc_dec_example_test_suite/blank_folder/test_none.py
2023-09-26 11:39:37.847 [debug] Found cached env for /usr/local/bin/python3.10
2023-09-26 11:39:37.847 [debug] Resolved /usr/local/bin/python3.10 from cache: {"name":"","location":"","kind":"global-other","executable":{"filename":"/usr/local/bin/python3.10","sysPrefix":"/usr/local/opt/python@3.10/Frameworks/Python.framework/Versions/3.10","ctime":1694448791180,"mtime":1694448791180},"display":"Python 3.10.13 64-bit","version":{"major":3,"minor":10,"micro":13,"release":{"level":"final","serial":0},"sysVersion":"3.10.13 (main, Aug 24 2023, 22:48:59) [Clang 14.0.3 (clang-1403.0.22.14.1)]"},"arch":3,"distro":{"org":""},"source":["path env var"],"id":"/usr/local/bin/python3.10","detailedDisplayName":"Python 3.10.13 64-bit"}
2023-09-26 11:39:37.848 [debug] Cached data exists KeyPrefix=Cache_Method_Output_E.ensureEnvironmentContainsPython-Args="/usr/local/bin/python3.10"-Arg-Separator-{"uri":{"$mid":1,"fsPath":"/Users/meganrogge/Repos/inc_dec_example_repo/inc_dec_example_test_suite","external":"file:///Users/meganrogge/Repos/inc_dec_example_repo/inc_dec_example_test_suite","path":"/Users/meganrogge/Repos/inc_dec_example_repo/inc_dec_example_test_suite","scheme":"file"},"name":"inc_dec_example_test_suite","index":0}
2023-09-26 11:39:37.894 [debug] Clearing context for python dependencies not installed: /Users/meganrogge/Repos/inc_dec_example_repo/inc_dec_example_test_suite/blank_folder/test_none.py
2023-09-26 11:39:37.979 [debug] Cached data exists KeyPrefix=Cache_Method_Output_b._selectIfLaunchedViaActivatedEnv-Args=true
2023-09-26 11:39:37.979 [debug] Found cached env for /usr/local/bin/python3.10
2023-09-26 11:39:37.979 [debug] Resolved /usr/local/bin/python3.10 from cache: {"name":"","location":"","kind":"global-other","executable":{"filename":"/usr/local/bin/python3.10","sysPrefix":"/usr/local/opt/python@3.10/Frameworks/Python.framework/Versions/3.10","ctime":1694448791180,"mtime":1694448791180},"display":"Python 3.10.13 64-bit","version":{"major":3,"minor":10,"micro":13,"release":{"level":"final","serial":0},"sysVersion":"3.10.13 (main, Aug 24 2023, 22:48:59) [Clang 14.0.3 (clang-1403.0.22.14.1)]"},"arch":3,"distro":{"org":""},"source":["path env var"],"id":"/usr/local/bin/python3.10","detailedDisplayName":"Python 3.10.13 64-bit"}
2023-09-26 11:39:38.031 [debug] Clearing context for python dependencies not installed: /Users/meganrogge/Repos/inc_dec_example_repo/inc_dec_example_test_suite/blank_folder/test_none.py

[eleanorjboyd]

question for @meganrogge or @bhavyaus, how long did you both wait to see if the tests would load? Usually what happens with mine is that I click on the test explorer icon then have to wait a few seconds for the screen that says "configure tests" to disappear and be replaced by the tests discovered. This load time is a problem I have noted and I am looking to make a change which I am discussing in this issue: #22007. The issue also has videos demonstrating what I mean by it resolving after a little lag time. If one of you could test to see if this is the case for you and there is just a delay that would be super helpful. Additionally would love your feedback on what UI change should be made to signal that loading is occurring. I was thinking a load icon somewhere (not sure where) but also maybe making it so the "configure tests" button doesn't appear would also help.

[meganrogge]

I had waited more than a minute I would say.

It's still not discovering tests. here's the full output:

023-09-28 09:58:01.181 [info] Experiment 'pythonTestAdapter' is active
2023-09-28 09:58:01.181 [info] Experiment 'pythonPromptNewFormatterExt' is active
2023-09-28 09:58:01.181 [info] Experiment 'pythonPromptNewToolsExt' is active
2023-09-28 09:58:01.181 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2023-09-28 09:58:01.182 [info] Test server listening.
2023-09-28 09:58:01.182 [info] Python interpreter path: /usr/local/bin/python3.10
2023-09-28 09:58:07.268 [info] Starting Pylance language server.
2023-09-28 10:57:41.193 [info] > conda info --json
2023-09-28 11:41:20.865 [info] Discover tests for workspace name: inc_dec_example_test_suite - uri: /Users/meganrogge/Repos/inc_dec_example_repo/inc_dec_example_test_suite
2023-09-28 11:41:20.865 [info] Running discovery for unittest using the new test adapter.
2023-09-28 11:41:20.911 [info] Discovering unittest tests with arguments: /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12711016/pythonFiles/unittestadapter/discovery.py,--port,62694,--uuid,75a1a244-b07d-44b5-84d9-2ed9b85253af,--udiscovery,-v,-s,.,-p,*test.py

2023-09-28 11:41:20.911 [info] > /usr/local/bin/python3.10 /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12711016/pythonFiles/unittestadapter/discovery.py --port 62694 --uuid 75a1a244-b07d-44b5-84d9-2ed9b85253af --udiscovery -v -s . -p *test.py
2023-09-28 11:41:20.911 [info] cwd: .
2023-09-28 11:41:21.582 [error] Subprocess exited unsuccessfully with exit code null and signal SIGSEGV
2023-09-28 11:41:21.582 [error] Subprocess exited unsuccessfully with exit code null and signal SIGSEGV. Creating and sending error discovery payload
2023-09-28 11:41:21.582 [error] Unittest test discovery error 
  
 The python test process was terminated before it could exit on its own, the process errored with: Code: null, Signal: SIGSEGV
2023-09-28 11:41:21.582 [info] ResultResolver EOT received for discovery.
2023-09-28 11:41:21.980 [info] Discover tests for workspace name: inc_dec_example_test_suite - uri: /Users/meganrogge/Repos/inc_dec_example_repo/inc_dec_example_test_suite
2023-09-28 11:41:21.980 [info] Running discovery for unittest using the new test adapter.
2023-09-28 11:41:22.040 [info] Discovering unittest tests with arguments: /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12711016/pythonFiles/unittestadapter/discovery.py,--port,62694,--uuid,a62ce555-7b74-4f45-9489-32e556001f03,--udiscovery,-v,-s,.,-p,*test.py

2023-09-28 11:41:22.040 [info] > /usr/local/bin/python3.10 /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12711016/pythonFiles/unittestadapter/discovery.py --port 62694 --uuid a62ce555-7b74-4f45-9489-32e556001f03 --udiscovery -v -s . -p *test.py
2023-09-28 11:41:22.040 [info] cwd: .
2023-09-28 11:41:22.486 [error] Subprocess exited unsuccessfully with exit code null and signal SIGSEGV
2023-09-28 11:41:22.486 [error] Subprocess exited unsuccessfully with exit code null and signal SIGSEGV. Creating and sending error discovery payload
2023-09-28 11:41:22.486 [error] Unittest test discovery error 
  
 The python test process was terminated before it could exit on its own, the process errored with: Code: null, Signal: SIGSEGV
2023-09-28 11:41:22.486 [info] ResultResolver EOT received for discovery.
2023-09-28 11:41:27.844 [info] Discover tests for workspace name: inc_dec_example_test_suite - uri: /Users/meganrogge/Repos/inc_dec_example_repo/inc_dec_example_test_suite/.vscode/settings.json
2023-09-28 11:41:27.844 [info] Running discovery for unittest using the new test adapter.
2023-09-28 11:41:27.887 [info] Discovering unittest tests with arguments: /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12711016/pythonFiles/unittestadapter/discovery.py,--port,62694,--uuid,e3bf2785-1b5d-46d8-86be-0a3e9ee331ed,--udiscovery,-v,-s,.,-p,*test*.py

2023-09-28 11:41:27.887 [info] > /usr/local/bin/python3.10 /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12711016/pythonFiles/unittestadapter/discovery.py --port 62694 --uuid e3bf2785-1b5d-46d8-86be-0a3e9ee331ed --udiscovery -v -s . -p *test*.py
2023-09-28 11:41:27.887 [info] cwd: .
2023-09-28 11:41:28.076 [error] Subprocess exited unsuccessfully with exit code null and signal SIGSEGV
2023-09-28 11:41:28.076 [error] Subprocess exited unsuccessfully with exit code null and signal SIGSEGV. Creating and sending error discovery payload
2023-09-28 11:41:28.077 [error] Unittest test discovery error 
  
 The python test process was terminated before it could exit on its own, the process errored with: Code: null, Signal: SIGSEGV
2023-09-28 11:41:28.077 [info] ResultResolver EOT received for discovery.
2023-09-28 11:41:28.256 [info] Discover tests for workspace name: inc_dec_example_test_suite - uri: /Users/meganrogge/Repos/inc_dec_example_repo/inc_dec_example_test_suite
2023-09-28 11:41:28.256 [info] Running discovery for unittest using the new test adapter.
2023-09-28 11:41:28.272 [info] Discovering unittest tests with arguments: /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12711016/pythonFiles/unittestadapter/discovery.py,--port,62694,--uuid,b0ec9933-406c-4e50-ae84-e4e54caaacf9,--udiscovery,-v,-s,.,-p,*test*.py

2023-09-28 11:41:28.272 [info] > /usr/local/bin/python3.10 /Applications/code-insiders-portable-data/extensions/ms-python.python-2023.17.12711016/pythonFiles/unittestadapter/discovery.py --port 62694 --uuid b0ec9933-406c-4e50-ae84-e4e54caaacf9 --udiscovery -v -s . -p *test*.py
2023-09-28 11:41:28.272 [info] cwd: .
2023-09-28 11:41:28.512 [error] Subprocess exited unsuccessfully with exit code null and signal SIGSEGV
2023-09-28 11:41:28.512 [error] Subprocess exited unsuccessfully with exit code null and signal SIGSEGV. Creating and sending error discovery payload
2023-09-28 11:41:28.512 [error] Unittest test discovery error 
  
 The python test process was terminated before it could exit on its own, the process errored with: Code: null, Signal: SIGSEGV
2023-09-28 11:41:28.512 [info] ResultResolver EOT received for discovery.

[eleanorjboyd]

I see that "The python test process was terminated before it could exit on its own, the process errored with: Code: null, Signal: SIGSEGV". It seems the issue is it doesn't show an error node- will investigate this. Thanks!

[eleanorjboyd]

reviewed this code and still not seeing how it could not produce an error node to display- could you send over the code you were testing it on? I will also add another logging item and see if that gives me more insight in insiders tomorrow.

[meganrogge]

we discussed and this happened because there was a segfault in one of my tests. commenting that out fixed it

[meganrogge]

I wonder if we could make this error more obvious

[eleanorjboyd]

this was a discussion more generally since I am not sure the way it displays it as a node in the test explorer is best- will find that issue and tag it here as we do discuss more.

[meganrogge]

feel free to close this if you are tracking it somewhere

[eleanorjboyd]

closing in favor of the mentioned issue