Logging with logpanel or logfile settings doesn't work

[vakokako]

Reopening #382

Describe the bug

Logging doesn't work, both for logpanel, and logfile.

To Reproduce

1. Set these properties in the folder settings.json file:

"testMate.cpp.log.logpanel": true,
"testMate.cpp.log.logfile": "/tmp/testMate.log",

2. Reopen the project so that new settings are in effect
3. Open side panel window to see project's tests
4. "/tmp/testMate.log" isn't created, there is no logging window in output for test extension

Desktop

• Extension Version: v4.4.1
• VS Code Version: 1.77.3
• Catch2 / Google Test / DOCTest Version:
• OS Type and Version: Ubuntu 22.04
• Using remote-ssh/docker/wsl?: nope

[emmenlau]

Same for me, with a different user account but similar setup of OS and VSCode.

[emmenlau]

Also, when I search for logFile in the sources, I find the only references in source code in

vscode-catch2-test-adapter/test/Common.ts

Line 184 in 3a0a336

if (k !== 'log.logfile' && k !== 'log.logSentry' && k !== 'log.userId')

. But there it is actually excluded and not included. Is it possible that the key logFile is even unused? Or am I on the wrong track?

[matepek]

That line is not related. This is the one: https://github.com/hbenl/vscode-test-adapter-util/blob/master/src/log.ts#L31
And I can still see the logs both for window and file but I'm using MacOS.

[matepek]

It is possible to try an earlier version of the extension or an earlier version of VSCode. that would help I believe.

[vakokako]

I tried up to version 4.0.0 and it still didn't work...

[yi-ge]

Same for me, vscode out: Couldn't write log file testMate.cpp.log: Error: EROFS: read-only file system, open 'testMate.cpp.log'

[matepek]

Installing ubuntu 22 is time consuming..
Do you guys have some issue and would need the log or just would like to see the logs?
Logpanel also nothing? Hard to think what could be the issue...

[yi-ge]

I need the log file.

[matepek]

Please state your OS Type and Version
@yi-ge , @emmenlau

[yi-ge]

Windows 11 x86_64
MacOS Arm64 13.5 Beta版(22G5027e)
@matepek

[matepek]

Okay so this is a multi platform issue which I cannot reproduce locally.
If someone would like to help me debugging, let me know. We can create a session.
Otherwise one can create a VM in which it is reproducible and share with me. :D

[matepek]

Any news on this front? It still works for me.

[johannes-fischer]

Also does not work for me on Ubuntu 20.04.

[matepek]

@johannes-fischer , In your linked issue you were able to quote log output. Where did you get it if it doesn't work for you?

[johannes-fischer]

As I wrote in the linked issue, I only was lucky to get logs sometimes:

I now sometimes get logs, but unreliably: I only see the logs in the output window early after a vs code restart, after some time the window vanishes from the drop-down list. Also, most of the restarts there are not logs at all.