@hugodutka

@evgeniy-scherbina ran into this. Basically he is running on a mac, and unable to run these tests locally. However it seems docker does not exist in our CI to run postgres?? I figured this might be resolved somehow to run the other PG tests. Do you have any recommendations to allow these tests to be run locally?

I'm ok if these tests are still skipped on mac CI, we just want them to being able to be run locally on Mac.

@Emyrk @evgeniy-scherbina These tests are failing because they are running as part of the in-mem test suite (test-go rather than test-go-pg). GitHub runners for macOS and Windows can't run Docker, since it requires Linux running in a VM, these runners are VMs themselves, and they don't support nested virtualization.

For a fix, I'd modify each failing test to include

if !dbtestutil.WillUsePostgres() {
	t.Skip("this test requires postgres")
}

And run the tests locally with DB=ci gotestsum ...

The tests do pass in CI in the PG suite because we use embedded postgres to set up the db before running them.

As a sidenote, we recently switched our macOS runners to run on depot, which uses physical hardware AFAIK, so we could set up Docker there eventually.

And one more thing - there's one test that has a hard dependency on Docker:

I'd skip it conditionally based on whether Docker is available.

@Emyrk @hugodutka fixed CI, could you pls. review it?

NOTE: I only removed linux build tags, I didn't touch pubsub_linux_test.go or other tests with linux_test.go suffix.