roachtest: node-postgres failed

[cockroach-teamcity]

Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout.

roachtest.node-postgres failed with artifacts on master @ 5c4a24e928c792bc3408aff56252a88ca65256fd:

(nodejs_postgres.go:171).func1: COMMAND_PROBLEM: exit status 2
test artifacts and logs in: /artifacts/node-postgres/run_1

Parameters:

• arch=amd64
• cloud=azure
• coverageBuild=false
• cpu=4
• encrypted=false
• metamorphicBufferedSender=false
• metamorphicLeases=default
• runtimeAssertionsBuild=true
• ssd=0
  Help

See: roachtest README

See: How To Investigate (internal)

Grafana is not yet available for azure clusters

/cc @cockroachdb/sql-foundations

This test on roachdash | Improve this report!

Jira issue: CRDB-49411

[rafiss]

  2 failing

  1) connection timeout
       releases newly connected clients if the queued already timed out:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/mnt/data1/node-postgres/packages/pg-pool/test/connection-timeout.js)
      at listOnTimeout (node:internal/timers:569:17)
      at process.processTimers (node:internal/timers:512:7)

  2) pool size of 1
       can only send 1 query at a time:

      Error: expected [ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ] to sort of equal [ 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1 ]
      + expected - actual

[rafiss]

This is the first time that the connection timeout test has flaked. Closing for now unless it becomes more frequent.