Visualisation of Tests breaks

[ilyakochik]

Behaviour

Whenever some of pytest parametrised test fail, they are not cleaned up before showing updated run and new text is printed on top of old

Steps to reproduce:

1. Setup paremetrised pytest
2. Run tests with failure
3. Fix failure
4. Run test again

Diagnostic data

Output for Python Test Log

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

backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]
backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]
backend/tests/test_pipeline.py::test_pipeline[inexpected]

8 tests collected in 0.39s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.Running pytest with args: ['-p', 'vscode_pytest', '--quiet', '--tb=short', '--rootdir=/Users/ilyakochik/Developer/refining-company/sql-refining', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[inexpected]']
.....F..                                                                 [100%]
=================================== FAILURES ===================================
___________________ test_pipeline[src.code.ingest_content.1] ___________________
backend/tests/test_pipeline.py:194: in test_pipeline
    assert correct[name] == captured[name], f"Snapshots '{name}' are different"
E   AssertionError: Snapshots 'src.code.ingest_content.1' are different
E   assert Strings are not equal:
E     --- 
E     +++ 
E     @@ -6,394 +5,0 @@
E     -    { "Query(0-accounts.sql:26:1)": {
E     -        "expressions": [
E     -          { "Expression(0-accounts.sql:28:5) = Expression(Binary_expression(Column(?.?.revenue), Column(?.?.contract_duration_days)))": {
E     -              "columns": [...
E     
E     ...Full output truncated (390 lines hidden), use '-vv' to show
=========================== short test summary info ============================
FAILED backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]
1 failed, 7 passed in 0.35s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.
==================================== ERRORS ====================================
_______________ ERROR collecting backend/tests/test_pipeline.py ________________
backend/tests/test_pipeline.py:190: in <module>
    @pytest.mark.parametrize("name,captured,correct", get_test_params())
backend/tests/test_pipeline.py:181: in get_test_params
    captured = capture_snapshots(config)
backend/tests/test_pipeline.py:150: in capture_snapshots
    server.main(**init["server:main"])
backend/src/server.py:99: in main
    session.load_codebase(codebase_path)
backend/src/workspace.py:22: in load_codebase
    self.queries_codebase = code.from_dir(self.path_codebase)
backend/src/code.py:111: in from_dir
    tree = ingest_content(tree, str(file.relative_to(dir)), file.read_text())
backend/tests/test_pipeline.py:124: in wrapper
    result = target(*args, **kwargs)
backend/src/code.py:127: in ingest_content
    queries=tree.queries() + updated_queries,
E   TypeError: 'list' object is not callable
------------------------------- Captured stderr --------------------------------
Loading codebase from /Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/inputs/codebase
=========================== short test summary info ============================
ERROR backend/tests/test_pipeline.py - TypeError: 'list' object is not callable
!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!
no tests collected, 1 error in 0.43s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]
backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]
backend/tests/test_pipeline.py::test_pipeline[inexpected]

8 tests collected in 0.32s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.Running pytest with args: ['-p', 'vscode_pytest', '--quiet', '--tb=short', '--rootdir=/Users/ilyakochik/Developer/refining-company/sql-refining', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]']
.                                                                        [100%]
1 passed in 0.31s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.Running pytest with args: ['-p', 'vscode_pytest', '--quiet', '--tb=short', '--rootdir=/Users/ilyakochik/Developer/refining-company/sql-refining', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[inexpected]']
........                                                                 [100%]
8 passed in 0.31s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]
backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]
backend/tests/test_pipeline.py::test_pipeline[inexpected]

8 tests collected in 0.33s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.Running pytest with args: ['-p', 'vscode_pytest', '--quiet', '--tb=short', '--rootdir=/Users/ilyakochik/Developer/refining-company/sql-refining', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[inexpected]']
........                                                                 [100%]
8 passed in 0.34s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]
backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]
backend/tests/test_pipeline.py::test_pipeline[inexpected]

8 tests collected in 0.37s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.Running pytest with args: ['-p', 'vscode_pytest', '--quiet', '--tb=short', '--rootdir=/Users/ilyakochik/Developer/refining-company/sql-refining', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[inexpected]']
F...FF.F                                                                 [100%]
=================================== FAILURES ===================================
___________________ test_pipeline[src.code.ingest_content.2] ___________________
backend/tests/test_pipeline.py:193: in test_pipeline
    assert name in captured, f"Snapshot '{name}' was not captured"
E   AssertionError: Snapshot 'src.code.ingest_content.2' was not captured
E   assert 'src.code.ingest_content.2' in {'src.code.ingest.0': '{\n  "files": { "0-accounts.sql": "<Tree>" },\n  "queries": [\n    { "Query(0-accounts.sql:26:1...s.industry" ] } ],\n          "alias": "industry_tech" } } ],\n    "reliability": 1,\n    "similarity": 0.95 } ]', ...}
___________________ test_pipeline[src.code.ingest_content.0] ___________________
backend/tests/test_pipeline.py:193: in test_pipeline
    assert name in captured, f"Snapshot '{name}' was not captured"
E   AssertionError: Snapshot 'src.code.ingest_content.0' was not captured
E   assert 'src.code.ingest_content.0' in {'src.code.ingest.0': '{\n  "files": { "0-accounts.sql": "<Tree>" },\n  "queries": [\n    { "Query(0-accounts.sql:26:1...s.industry" ] } ],\n          "alias": "industry_tech" } } ],\n    "reliability": 1,\n    "similarity": 0.95 } ]', ...}
___________________ test_pipeline[src.code.ingest_content.1] ___________________
backend/tests/test_pipeline.py:193: in test_pipeline
    assert name in captured, f"Snapshot '{name}' was not captured"
E   AssertionError: Snapshot 'src.code.ingest_content.1' was not captured
E   assert 'src.code.ingest_content.1' in {'src.code.ingest.0': '{\n  "files": { "0-accounts.sql": "<Tree>" },\n  "queries": [\n    { "Query(0-accounts.sql:26:1...s.industry" ] } ],\n          "alias": "industry_tech" } } ],\n    "reliability": 1,\n    "similarity": 0.95 } ]', ...}
__________________________ test_pipeline[inexpected] ___________________________
backend/tests/test_pipeline.py:197: in test_pipeline
    assert not extra_snapshots, f"Unexpected snapshots captured: {extra_snapshots}"
E   AssertionError: Unexpected snapshots captured: {'src.code.ingest.1', 'src.code.ingest.0', 'src.code.ingest.2'}
E   assert not {'src.code.ingest.0', 'src.code.ingest.1', 'src.code.ingest.2'}
=========================== short test summary info ============================
FAILED backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]
FAILED backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]
FAILED backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]
FAILED backend/tests/test_pipeline.py::test_pipeline[inexpected] - AssertionE...
4 failed, 4 passed in 0.34s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]
backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]
backend/tests/test_pipeline.py::test_pipeline[inexpected]

8 tests collected in 0.31s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.Running pytest with args: ['-p', 'vscode_pytest', '--quiet', '--tb=short', '--rootdir=/Users/ilyakochik/Developer/refining-company/sql-refining', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[inexpected]']

no tests ran in 0.31s
ERROR: not found: /Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.2]
(no match in any of [<Module test_pipeline.py>])

ERROR: not found: /Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.0]
(no match in any of [<Module test_pipeline.py>])

ERROR: not found: /Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest_content.1]
(no match in any of [<Module test_pipeline.py>])

Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.0]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.1]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]
backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.2]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]
backend/tests/test_pipeline.py::test_pipeline[inexpected]

8 tests collected in 0.31s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.Running pytest with args: ['-p', 'vscode_pytest', '--quiet', '--tb=short', '--rootdir=/Users/ilyakochik/Developer/refining-company/sql-refining', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[inexpected]']
........                                                                 [100%]
8 passed in 0.31s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.0]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.1]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]
backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.2]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]
backend/tests/test_pipeline.py::test_pipeline[inexpected]

8 tests collected in 0.32s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.0]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.1]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]
backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]
backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.2]
backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]
backend/tests/test_pipeline.py::test_pipeline[inexpected]

8 tests collected in 0.31s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.Running pytest with args: ['-p', 'vscode_pytest', '--quiet', '--tb=short', '--rootdir=/Users/ilyakochik/Developer/refining-company/sql-refining', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.logic.compare.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.1]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.code.ingest.2]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[src.sql.parse.0]', '/Users/ilyakochik/Developer/refining-company/sql-refining/backend/tests/test_pipeline.py::test_pipeline[inexpected]']
........                                                                 [100%]
8 passed in 0.32s
Starting now, all test run output will be sent to the Test Result panel, while test discovery output will be sent to the "Python" output channel instead of the "Python Test Log" channel. The "Python Test Log" channel will be deprecated within the next month. See https://github.com/microsoft/vscode-python/wiki/New-Method-for-Output-Handling-in-Python-Testing for details.

[karthiknadig]

@alexr00 This looks like a bug in TreeView rendering. I am actually seeing the same where the getChildren with undefined sometimes keeps the old tree as is. Started happening recently.

@connor4312 FYI.

[alexr00]

@karthiknadig I don't think that the Test view uses the TreeView from the VS Code extension API. @connor4312 is that correct?