Skip to content
test

refactor: Use new URL for connection string parsing #632

Sign in to view logs

refactor: Use new URL for connection string parsing

refactor: Use new URL for connection string parsing #632

Re-run triggered October 12, 2025 06:01
@porsagerporsager
#1127
denghongcai:refactor-url-parse
Status Failure
Total duration 4m 7s
Artifacts –

test.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

54 errors
Node v16 on PostgreSQL v13
Process completed with exit code 1.
Node v16 on PostgreSQL v12
Process completed with exit code 1.
Node v21 on PostgreSQL v12
Process completed with exit code 1.
Node v12 on PostgreSQL v12
Process completed with exit code 1.
Node v20 on PostgreSQL v14
Process completed with exit code 1.
Node v23 on PostgreSQL v12
Process completed with exit code 1.
Node v21 on PostgreSQL v13
Process completed with exit code 1.
Node v16 on PostgreSQL v17
Process completed with exit code 1.
Node v18 on PostgreSQL v12
Process completed with exit code 1.
Node v23 on PostgreSQL v17
Process completed with exit code 1.
Node v12 on PostgreSQL v15
Process completed with exit code 1.
Node v16 on PostgreSQL v15
Process completed with exit code 1.
Node v20 on PostgreSQL v17
Process completed with exit code 1.
Node v12 on PostgreSQL v13
Process completed with exit code 1.
Node v12 on PostgreSQL v14
Process completed with exit code 1.
Node v16 on PostgreSQL v16
Process completed with exit code 1.
Node v18 on PostgreSQL v13
Process completed with exit code 1.
Node v14 on PostgreSQL v15
Process completed with exit code 1.
Node v16 on PostgreSQL v14
Process completed with exit code 1.
Node v20 on PostgreSQL v13
Process completed with exit code 1.
Node v20 on PostgreSQL v16
Process completed with exit code 1.
Node v23 on PostgreSQL v15
Process completed with exit code 1.
Node v14 on PostgreSQL v16
Process completed with exit code 1.
Node v14 on PostgreSQL v12
Process completed with exit code 1.
Node v14 on PostgreSQL v17
Process completed with exit code 1.
Node v20 on PostgreSQL v12
Process completed with exit code 1.
Node v18 on PostgreSQL v17
Process completed with exit code 1.
Node v18 on PostgreSQL v16
Process completed with exit code 1.
Node v22 on PostgreSQL v13
Process completed with exit code 1.
Node v21 on PostgreSQL v17
Process completed with exit code 1.
Node v24 on PostgreSQL v13
Process completed with exit code 1.
Node v18 on PostgreSQL v15
Process completed with exit code 1.
Node v21 on PostgreSQL v14
Process completed with exit code 1.
Node v22 on PostgreSQL v12
Process completed with exit code 1.
Node v23 on PostgreSQL v14
Process completed with exit code 1.
Node v21 on PostgreSQL v15
Process completed with exit code 1.
Node v22 on PostgreSQL v15
Process completed with exit code 1.
Node v14 on PostgreSQL v14
Process completed with exit code 1.
Node v14 on PostgreSQL v13
Process completed with exit code 1.
Node v24 on PostgreSQL v12
Process completed with exit code 1.
Node v21 on PostgreSQL v16
Process completed with exit code 1.
Node v12 on PostgreSQL v16
Process completed with exit code 1.
Node v22 on PostgreSQL v17
Process completed with exit code 1.
Node v24 on PostgreSQL v14
Process completed with exit code 1.
Node v20 on PostgreSQL v15
Process completed with exit code 1.
Node v24 on PostgreSQL v16
Process completed with exit code 1.
Node v18 on PostgreSQL v14
Process completed with exit code 1.
Node v24 on PostgreSQL v17
Process completed with exit code 1.
Node v22 on PostgreSQL v14
Process completed with exit code 1.
Node v22 on PostgreSQL v16
Process completed with exit code 1.
Node v24 on PostgreSQL v15
Process completed with exit code 1.
Node v23 on PostgreSQL v13
Process completed with exit code 1.
Node v12 on PostgreSQL v17
Process completed with exit code 1.
Node v23 on PostgreSQL v16
Process completed with exit code 1.