Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some tests are not displayed #103

Closed
vakokako opened this issue Jun 26, 2019 · 13 comments
Closed

Some tests are not displayed #103

vakokako opened this issue Jun 26, 2019 · 13 comments
Labels
invalid This doesn't seem right

Comments

@vakokako
Copy link

When I refresh the tests toolbar, it doesn't show all tests I have in the specified folder.

My settings are:

"catch2TestExplorer.executables": [
    {
        "name": "${filename}",
        "pattern": "/absoluteTestFolderPath/*{test,Test,TEST}*"
    }
]

The logpanel output for the not found tests is the following:

[2019-06-26 18:47:42.655] [WARN] [at load.suiteCreationAndLoadingTasks.push.c2fs.isNativeExecutableAsync.then._createSuiteByUri.then (/home/user/.vscode/extensions/matepek.vscode-catch2-test-adapter-2.5.0/out/src/TestExecutableInfo.js:73:38)] Not a test executable: /absoluteTestFolderPath/HistogramTest reason: [Error: FsWrapper.spawnAsync signal: SIGABRT
	at ChildProcess.<anonymous> (/home/user/.vscode/extensions/matepek.vscode-catch2-test-adapter-2.5.0/out/src/FSWrapper.js:36:24)
	at ChildProcess.emit (events.js:182:13)
	at maybeClose (internal/child_process.js:961:16)
	at Socket.ChildProcess.spawn.stream.socket.on (internal/child_process.js:380:11)
	at Socket.emit (events.js:182:13)
	at Pipe.Socket._destroy._handle.close [as _onclose] (net.js:596:12)]
@matepek
Copy link
Owner

matepek commented Jun 26, 2019

Can you run your test executable manually with --help?

@vakokako
Copy link
Author

vakokako commented Jun 27, 2019

Yes, it produces standart google test --help output

@matepek
Copy link
Owner

matepek commented Jun 27, 2019

How long does it take to produce that? If shorter than 5 sec I have no idea. Can you send me the exec? What kind of os. ...

@matepek matepek added the invalid This doesn't seem right label Jun 29, 2019
@matepek
Copy link
Owner

matepek commented Jul 7, 2019

Let me know if you still have the issue

@matepek matepek closed this as completed Jul 7, 2019
@vakokako
Copy link
Author

vakokako commented Jul 18, 2019

The issue still remains. The exec is super fast <1s, I can send it to you

@matepek
Copy link
Owner

matepek commented Jul 18, 2019

It is welcomed

@vakokako
Copy link
Author

ImageWriterTest.zip

@matepek
Copy link
Owner

matepek commented Jul 19, 2019

linux?

@vakokako
Copy link
Author

vakokako commented Jul 22, 2019

yes, Ubuntu 18

@matepek matepek reopened this Jul 29, 2019
@vakokako
Copy link
Author

vakokako commented Aug 14, 2019

I finally found why this was happening. The code outside of google testing was sending the exception and crashed the executable, so the catch2 script thought it wasn't an executable.
Could the extension handle that and still show that this test executable has crashed?

@vakokako
Copy link
Author

Also the exception was sent because of not getting the environment variables that cannot be set with "env", could this also be implemented? See details: #116

@vakokako vakokako reopened this Aug 14, 2019
@matepek
Copy link
Owner

matepek commented Aug 14, 2019

Sorry, but my linux VM is deep inside cupboard. :)

Check my comment on the issue you mentioned.

Let me know if you have any questions.

@matepek matepek closed this as completed Aug 14, 2019
@vakokako
Copy link
Author

I think I mixed too many things here, will create a new, more clear version)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants