Skip to content

configurable upper bound on locking attempt timeout #215

configurable upper bound on locking attempt timeout

configurable upper bound on locking attempt timeout #215

Triggered via pull request October 28, 2024 18:27
Status Failure
Total duration 1m 4s
Artifacts

regression.yml

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

Annotations

20 errors and 10 warnings
PostgreSQL 9.5
Process completed with exit code 1.
PostgreSQL 9.5
Process completed with exit code 2.
PostgreSQL 9.6
Process completed with exit code 2.
PostgreSQL 9.6
Process completed with exit code 1.
PostgreSQL 10
Process completed with exit code 1.
PostgreSQL 10
Process completed with exit code 2.
PostgreSQL 14
Process completed with exit code 2.
PostgreSQL 14
Process completed with exit code 1.
PostgreSQL 17
Process completed with exit code 1.
PostgreSQL 17
Process completed with exit code 2.
PostgreSQL 15
Process completed with exit code 1.
PostgreSQL 15
Process completed with exit code 2.
PostgreSQL 12
Process completed with exit code 1.
PostgreSQL 12
Process completed with exit code 2.
PostgreSQL 11
Process completed with exit code 1.
PostgreSQL 11
Process completed with exit code 2.
PostgreSQL 13
Process completed with exit code 2.
PostgreSQL 13
Process completed with exit code 1.
PostgreSQL 16
Process completed with exit code 2.
PostgreSQL 16
Process completed with exit code 1.
PostgreSQL 9.5
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PostgreSQL 9.6
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PostgreSQL 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PostgreSQL 14
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PostgreSQL 17
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PostgreSQL 15
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PostgreSQL 12
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PostgreSQL 11
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PostgreSQL 13
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PostgreSQL 16
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/