ConnectionPoolTest fails on gitlab.com CI
I'm working on a Pleroma fork hosted on gitlab.com. I've made a few attempts to get the test suite running there, but I'm stuck:
1) test connection limit is respected with concurrent requests (Pleroma.Gun.ConnectionPoolTest)
test/pleroma/gun/connection_pool_test.exs:50
** (ExUnit.TimeoutError) test timed out after 300000ms. You can change the timeout:
1. per test by setting "@tag timeout: x" (accepts :infinity)
2. per test module by setting "@moduletag timeout: x" (accepts :infinity)
3. globally via "ExUnit.start(timeout: x)" configuration
4. by running "mix test --timeout x" which sets timeout
5. or by running "mix test --trace" which sets timeout to infinity
(useful when using IEx.pry/0)
where "x" is the timeout given as integer in milliseconds (defaults to 60_000).
code: capture_log(fn ->
stacktrace:
test/pleroma/gun/connection_pool_test.exs:92: anonymous fn/2 in Pleroma.Gun.ConnectionPoolTest."test connection limit is respected with concurrent requests"/1
test/pleroma/gun/connection_pool_test.exs:92: anonymous fn/0 in Pleroma.Gun.ConnectionPoolTest."test connection limit is respected with concurrent requests"/1
(ex_unit) lib/ex_unit/capture_log.ex:80: ExUnit.CaptureLog.capture_log/2
test/pleroma/gun/connection_pool_test.exs:61: (test)
(ex_unit) lib/ex_unit/runner.ex:355: ExUnit.Runner.exec_test/1
(stdlib) timer.erl:166: :timer.tc/1
(ex_unit) lib/ex_unit/runner.ex:306: anonymous fn/4 in ExUnit.Runner.spawn_test_monitor/4
I've already increased the timeout to 5 minutes (@tag timeout: 300_000
) which seems unreasonably long for this test, but it still times out.
The test runs locally just fine.
I wonder if there's something different about the CI environment. So far it's just a verbatim clone of the develop branch.