Test Explorer always reloading tests

[thiagoperroni]

The UI stays on this state forever. The workspace has only a ceedling initial project with only one test. I got no problems running tests over the terminal.

[numaru]

In which terminal do you use Ceedling? For now the ext use 'cmd.exe' as default shell. Also Ceedling (and gcc by default) must be accessible in this shell to get the list of test (and execute them later).

[numaru]

The shell can now be configured with shellPath option. Can I close this issue?

[thiagoperroni]

Sorry for the delay.

I use Ceedling on 'cmd.exe'. Using shellPath option as default (null), the problem is the same I reported previously.

Configuring shellPath with the 'cmd.exe' path, I got this new error:

At least it has an error message now. I'll try some more things before give up.

Thanks for your attention

[numaru]

The 'cmd.exe' in shellPath doesn't work. I did a quick and dirty implementation because i'm waiting for the next release of nodejs which should handle shells correctly. To use cmd.exe as shell, do not define the option.

For now there is no logs in the extension. Also i need to reproduce the error to be able to fix it. Can you explain how did you manage to get ceedling working with cmd.exe? I tried to install ruby + gem install ceedling but the gcc toolchain was missing out of the box. That's why i was assuming you would use another shell (mingw/msys2 or bash/wsl).

Can you run ceedling files:test?

[aenima1891]

I've the same problem. I'm using cmd.exe by NOT defining the shell option. I can run ruby and gcc from shell cmd.exe

but the test explorer is always loading test.

I've installed ruby by https://rubyinstaller.org/ with default options

[numaru]

Thanks, i was able to reproduce it and patch it ✌. You should now be able to run from cmd.exe (shellPath not set). If one of you can confirm, I will let this issue closed.

[aenima1891]

It works! Thank you!

[thiagoperroni]

It worked for me too! Thank you so much!