[darcs-devel] my problems with tests that run ssh/curl

Ganesh Sittampalam ganesh at earth.li
Sun Jul 12 01:11:39 UTC 2020


As I mentioned in a different thread a while ago, I currently have
problems running the tests on Windows.

The problem is with a tool called "SentryBay" that I have to run to be
able to work from home. It injects some low level driver called
epinject.sys into every process that seems to cause network-using tools
in the mingw stack to just lock up eating CPU when run.

I will try to get this reported and fixed but it's likely to be a slow
process, and in the meantime the only way I can get around it is to
reboot. I've had the problem for ~1 year but of course in the past few
months it's had much more impact.

It turns out that quite a few of our non-network tests nevertheless do
run commands like ssh and curl for various reasons. One example is
issue2545_command-execution-via-ssh-uri which is fairly obvious but
there are several others.

I was vaguely wondering about just making those tests into "network"
tests that I then wouldn't run by default. It's not a great solution as
the tests don't generally genuinely rely on the network. Or I could add
a new kind of classification, perhaps only locally.

Any suggestions/opinions welcome..


More information about the darcs-devel mailing list