Skip to content

Conversation

@adelosa
Copy link
Contributor

@adelosa adelosa commented Oct 24, 2016

I'm using the tool on Windows and receiving the error as documented in #16
The following pull request seems to fix the issue with the invalid signal.

  • Assumes all other platforms work with sigint instead of sigterm
  • testcases with os.fork are skipped on Windows

* Assumes all other platforms work with sigint instead of sigterm
* testcases are broken on Windows due to use of os.fork
@coveralls
Copy link

Coverage Status

Coverage decreased (-1.4%) to 83.219% when pulling 5d1eac3 on adelosa:fix-windows-support into 738c8eb on tk0miya:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-1.4%) to 83.219% when pulling 4d3ef9c on adelosa:fix-windows-support into 738c8eb on tk0miya:master.

@tk0miya tk0miya merged commit e3b3120 into tk0miya:master Jan 12, 2017
@tk0miya
Copy link
Owner

tk0miya commented Jan 12, 2017

Thanks!

@adelosa adelosa deleted the fix-windows-support branch October 30, 2021 04:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants