Daniel Hahler

I haven't tested it myself, but apparently it needs adjustments, and/or shows incompatibilities with Vim's profiling output that is used. Some output from your CI job: ``` Script line does...

Is this reproducible, or something flaky? For reference: ``` /home/travis/virtualenv/python3.6.3/bin/covimerage run nvim -Nu test/vimrc -c 'Vader! test/**' Running cmd: nvim -Nu test/vimrc -c 'Vader! test/**' --cmd 'profile start /tmp/covimerage.profile.lh0u_yez' --cmd...

@wsdjeg did it start to happen only recently? Do you know what change triggered it then? Do you have a reference to the last good build?

Should be supported in general, but might be buggy/broken. Try running it with `-l debug`.

btw: having this (Windows) tested on CI via GitHub actions would be good I think - in case you feel like contributing this.

Yes. Currently it is using CircleCI, which could be kept, but we could switch to GitHub actions for testing on Windows. As for the issue: also try `set -x` (or...

> FWIW, from [release page](https://github.com/Vimjas/covimerage/releases), it says the latest version is 0.1.6. But on my action workflow, `covimerage --version` says 0.2.1. I'm not understanding this mimatch. I've pushed missing tags...

Thanks already. More debug logging would be good. Can you try `type .coverage_covimerage` after the command, which should display the output file, if any?

> I could retrieve profile output as follows: > > https://gist.github.com/rhysd/d550409c4eb22a66cac97cc1a1cb6748 `covimerage write_coverage profile.txt` works with that locally for me (on Linux), exiting with 0.

> I don't know why this line was not output: > > https://github.com/Vimjas/covimerage/blob/83018f323834e678f69bcc3daf16c92ccae6a67a/covimerage/cli.py#L147 This only happens with "covimerage run", but you are using "covimerage write_coverage", aren't you?