Hi syphilis, is there an environment variable set when running under 'make test'? If there is you could use that to control a skip_all directive in the test file. (Assumes that make test uses the Test::More harness).
I have used this technique to skip tests requiring external resources when running under CI. Perhaps it contains a clue.
The way forward always starts with a minimal test.
| [reply]
[d/l]
[select] |
My only means of escape from this hang (AFAIK) is to hit Ctrl-C, which kills the entire 'make test' process - meaning that none of the other ensuing tests are run.
You could just kill the offending test script process using the task manager or some other similar tool. For instance, I like Sysinternals Process Explorer (procexp) which shows processes as a tree and so it is easy to find the blocking child and kill it.
| [reply] |
You could just kill the offending test script process using the task manager or some other similar tool
Yes, my original post was built around a false assumption - namely, that Ctrl-C was the only way I could escape from the hang.
As salva suggested, procexp, makes it quite easy to select and kill the appropriate process.
One can even double check that one has selected the correct perl process (prior to killing that process) by looking at its command line, which is displayed under its "Properties".
Thank you, salva.
Thanks also to 1nickt for a handy idea. (1nickt's idea was more in line with what I initially expected was going to be needed.)
Cheers,
Rob
| [reply]
[d/l] |