search

numaru / vscode-ceedling-test-adapter

Ceedling Test Adapter for the VS Code Test Explorer
MIT License
37 stars 13 forks source link

Tests can get "stuck" and appear to run endlessly #125

Open jnz86 opened 8 months ago

jnz86 commented 8 months ago

Using Linux Mint host, remote development container using Ubunutu.

  1. Debugging works fine, ending the session does not show the extension that anything has ended. The timer for how long the test has run continues forever, until the STOP button is pressed.

  2. Running a test rapidly, will result in the same. The last run test ends. The previous tests will not run and will show the timer counting up forever. Again, pressing the STOP button is the resolution.

See video: https://github.com/numaru/vscode-ceedling-test-adapter/assets/26825637/4feed85d-3e83-438c-a1db-cce2371d7e54 (On my own machine and Firefox, this link does not work, I had to download to view it)

Relevant portion of my launch.json

        {
            "name": "Ceedling Test Explorer Debug",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/build/test/ceedling/test/out/${command:ceedlingExplorer.debugTestExecutable}",
            "args": [],
            "stopAtEntry": true,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "externalConsole": false,
            "MIMode": "gdb",
            "miDebuggerPath": "/usr/bin/gdb",
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": false
                }
            ]
        }

I didn't know if this was known, or unavoidable, or there is a solution.