Tests are not working anymore with version > 11

[robfrank]

Expected Behaviour
I'm one of the maintainer of ArcadeDB where some time ago we added some integration tests using TC for node to test our PgSQL endpoint.
Tests are running fine with 10.28.0 version of TC and we expect that they could run fine with 11.x version

Actual Behaviour
Actually, with 11.x versions, the container is started BUT it is not reachable by test code

Testcontainer Logs

  console.log
      testcontainers [DEBUG] [78555ed063d7] Created container for image "arcadedata/arcadedb:latest" +42ms

      at Logger.debug [as logger] (node_modules/debug/src/common.js:113:10)

  console.log
      testcontainers [INFO] [78555ed063d7] Starting container for image "arcadedata/arcadedb:latest"... +0ms

      at Logger.debug [as logger] (node_modules/debug/src/common.js:113:10)

  console.log
      testcontainers [DEBUG] [78555ed063d7] Starting container... +0ms

      at Logger.debug [as logger] (node_modules/debug/src/common.js:113:10)

  console.log
      testcontainers [DEBUG] [78555ed063d7] Started container +100ms

      at Logger.debug [as logger] (node_modules/debug/src/common.js:113:10)

  console.log
      testcontainers [INFO] [78555ed063d7] Started container for image "arcadedata/arcadedb:latest" +0ms

      at Logger.debug [as logger] (node_modules/debug/src/common.js:113:10)

  console.log
      testcontainers [DEBUG] [78555ed063d7] Waiting for container to be ready... +6ms

      at Logger.debug [as logger] (node_modules/debug/src/common.js:113:10)

  console.log
      testcontainers [DEBUG] [78555ed063d7] Waiting for HTTP... +1ms

      at Logger.debug [as logger] (node_modules/debug/src/common.js:113:10)

 FAIL  src/js-pg-e2e.test.js (60.392 s)
  ● E2E tests using pg client › should run simple query

    thrown: "Exceeded timeout of 60000 ms for a hook.
    Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."

       8 |   let postgresClient;
       9 |
    > 10 |   beforeAll(async () => {
         |   ^
      11 |     arcadedbContainer = await new GenericContainer("arcadedata/arcadedb:latest")
      12 |       .withExposedPorts(2480, 6379, 5432, 8182)
      13 |       .withEnvironment({

      at beforeAll (src/js-pg-e2e.test.js:10:3)
      at Object.describe (src/js-pg-e2e.test.js:4:1)

Steps to Reproduce
test code: https://github.com/ArcadeData/arcadedb/tree/main/e2e-js
test run on dependabot pr: https://github.com/ArcadeData/arcadedb/actions/runs/16098018018/job/45423514968?pr=2333

Environment Information

• Operating System: linux and mac
• Docker Version:
• Node version: 22
• Testcontainers version: 11.x (works fine until 10.28.0)

[cristianrgreco]

Hi Rob, the logs only show that the wait strategy timed out. Are there no logs from the container?

EDIT: I see you've shared a nice repro, I'll take a look when I can

[watford-ep]

Seeing this with neo4j containers as well on 11.X

[cristianrgreco]

@watford-ep Unlike arcadedb which doesn't have a testcontainers module, neo4j tests are run as part of every build and there aren't any known issues. If you've found one, feel free to raise a new issue.

---

I was just looking at Rob's issue and the issue is that Undici is failing to convert the 204 (no content) response to a Fetch response because the body isn't null. I'm working on a fix now.

[robfrank]

So the fault it's mine that i put some content in a 204 response. ARGH!

[cristianrgreco]

So the fault it's mine that i put some content in a 204 response

IIRC it's a cardinal sin.. 😜

I'm going to release the fix anyway because it was an unintended breaking change between 10.x and 11.x. If an API does return a 204 with content, there's currently no way for a user to configure it to pass, which isn't what we want.

[cristianrgreco]

Can confirm it's working now with 11.2.1. Thanks for raising!

 PASS  src/js-pg-e2e.test.js (9.719 s)
  E2E tests using pg client
    ✓ should run simple query (139 ms)
    ✓ should run schema query (118 ms)

[robfrank]

Thank you very much!