Issues in re-running tests about vscode-catch2-test-adapter HOT 7 CLOSED

Please set: catch2TestExplorer.logfile and reproduce the bug.
Attach the log file and describe how can it be reproduced step by step.
Thanks.

from vscode-catch2-test-adapter.

Anyway, probably one of your tests is in an infinite loop or stuck. Try to set catch2TestExplorer .defaultRunningTimeoutSec: 10 and see whats happening.

from vscode-catch2-test-adapter.

I'm afraid the log file isn't generated, I will try setting the timeout, that's definitely an idea I didn't think of. I'll let you know how it works out. Thanks

from vscode-catch2-test-adapter.

👍Let me know about the result.

That's weird, it should work. Did you set a valid path? (with existing directories) Does your process have write access for that directory?

from vscode-catch2-test-adapter.

Ok, so I have added the logfile entry into the settings, VsCode then throws this error

This is of course in my build directory and therefore the process most definitely has access to write to it.

Once actually running tests with that setting, VsCode then throws further errors;

Tests can no longer be run until this entry is removed from the settings.

I do however, have a set of logs from the log panel. How can I send this to you securely? It has all manner of test details within it, I'd rather not post publicly.

Thanks

from vscode-catch2-test-adapter.

Hello,

I see, thanks for the detailed explanation, this would be helpful, however I don't give support for forks. My extension is this and you are using this.

It can be easily happen that the bug also exists in case of my extension (especially because linux is part of the issue), but I hope you understand that I don't want to care about forks.

logfile: Have you tried using an absolute path?

If you check and prove that the problem still exists I will reopen this issue.

from vscode-catch2-test-adapter.

Ah! I'm sorry, I hadn't realised it was a fork. I'll update the extension to use yours and update the thread appropriately. Thanks

from vscode-catch2-test-adapter.