cli: ctrl-c for 'popper --parallel' not working on 2.7

[ivotron]

It seems like the issue is due to pythonfutures as it doesn't handle KeyBoard Interruprts. It is evident from this PR, agronholm/pythonfutures#50 . It is not specific to ProcessPool / ThreadPool, but looks like an issue of pythonfutures module.

[JayjeetAtGithub]

@ivotron Can you please give me some insight about how to approach solving this issue? I have found that the SIGINT signal is not getting caught by the signal_handler properly. Sometimes, after the test script completed executing, the signal gets caught and the logic in the signal_handler follows. #595 is failing due to this.

[JayjeetAtGithub]

This seems like an issue in pythonfutures module

[ivotron]

Since --parallel is not a critical feature, I would vote for implementing a workaround for now: if --parallel is given, inspect the workflow and, if a HostRunner action is part of the workflow, then show a message and exit. We then comment this on the corresponding test, make a reference to this issue in the comments of the test, and we keep this issue open until we can keep investigating

[JayjeetAtGithub]

@ivotron Ok !

[JayjeetAtGithub]

@ivotron The SIGINT is not caught by either of the runners. All of the runners are having similar behaviour like HostRunner, when executed in python2.7.

[ivotron]

I see. In this case then let's disable --parallel for 2.7 altogether, so we can investigate what's going on later

[JayjeetAtGithub]

@ivotron i will disable interrupt tests for --parallel

[ivotron]

closed as byproduct of closing #742