tests\async\tasyncssl.nim no longer works on windows (appveyor)

[skilchen]

The CI runs on appveyor systematically fail on tests\async\tasyncssl.nim

appveyor probably upgraded its openssl to Win64 OpenSSL v1.1.1

If you try to use the dlls (libcrypto-1_1-x64.dll and libssl-1_1-x64.dll) from https://slproweb.com/download/Win64OpenSSL_Light-1_1_1.exe you get the same error running the tests locally.

With the dlls from https://nim-lang.org/download/dlls.zip (libeay64.dll, ssleay64.dll) or from https://slproweb.com/download/Win64OpenSSL_Light-1_1_0i.exe (libcrypto-1_1-x64.dll, libssl-1_1-x64.dll) the tests\async\tasyncssl.nim passes.

[timotheecour]

indeed, it affects a number of PR's;

• how come Nim shows Build Status as pasing?
  

example failure

https://ci.appveyor.com/project/Araq/nim/builds/20275193

Test "tests/async\tasyncssl.nim" in category "async"
Failure: reExitcodesDiffer
Expected:
exitcode: 0
Gotten:
exitcode: 1
Output:
tasyncssl.nim(63)        tasyncssl
system.nim(3930)         failedAssertImpl
system.nim(3923)         raiseAssert
system.nim(2970)         sysFatal
Error: unhandled exception: C:\projects\nim\tests\async\tasyncssl.nim(63, 10) `msgCount == swarmSize * messagesToSend`  [AssertionError]

maybe related

• Fix async SSL tests #8845 (comment) comment by @dom96

This isn't a valid fix though. The problem lies somewhere else and this PR is just working around it by accident.

[dom96]

I committed a workaround.

[Araq]

Well, a disabled test is a disabled test and it works with newer DLLs. Disabled tests are bad but not bugs.