Re-enable Firebird tests (Issue178_Firebird)

[0xced]

No description provided.

[0xced]

Well, it looks like running Firebird in a docker container on AppVeyor is not as easy as it ought to be. 😣

Downloading and configuring and running Firebird could also be a possibility, but that's quite a lot of code.

[mgravell]

I'm fine with it, but appveyor says "nope"

specifically it says:

docker: error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.40/containers/create?name=Dapper.Tests.Firebird: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

[0xced]

Unfortunately I'm not familiar enough with AppVeyor.

There's this //./pipe/docker_engine access denied? discussion on the AppVeyor forum but it doesn't seem to really offer a solution.

Alternatively, Firebird could probably be downloaded, configured and executed with scripts, like nhibernate-core does. But that's too much YAML and PowerShell for me. 😅

[mgravell]

Me too :)

I think this is one of those things where if it is going to fight us, it is going to stay disabled (unless @NickCraver has some magic CI-jitsu to employ)

[NickCraver]

Indeed this isn't something we can really pull in unless the platform already runs the server, we just don't have the test environment from it. Even in say GitHub Actions we have another version of the problem: we can't build and test .NET Framework (Windows) because service containers can only run on Ubuntu. Clients testing against server bits isn't something well supported on most test platforms, unfortunately :(