Skip to content

fix(se): gracefully terminate pg connections on SIGINT and SIGTERM #4349

fix(se): gracefully terminate pg connections on SIGINT and SIGTERM

fix(se): gracefully terminate pg connections on SIGINT and SIGTERM #4349

Triggered via pull request June 13, 2025 21:41
Status Success
Total duration 8m 47s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

test-schema-engine.yml

on: pull_request
Matrix: test-linux-push
Waiting for pending jobs
Matrix: test-linux
Matrix: test-mongodb-schema-connector
Matrix: test-windows
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
sqlite on Linux / sqlite
Failed to restore: getCacheEntry failed: Cache service responded with 503
sqlite on Linux / sqlite
Failed to restore: getCacheEntry failed: Cache service responded with 503
mysql_8 on Linux / mysql_8
Failed to save: reserveCache failed: Cache service responded with 503
mysql_8 on Linux / mysql_8
Failed to restore: getCacheEntry failed: Cache service responded with 503
mysql_8 on Linux / mysql_8
Failed to restore: getCacheEntry failed: Cache service responded with 503
postgres16 on Linux / postgres16
Failed to save: reserveCache failed: Cache service responded with 503
postgres16 on Linux / postgres16
Failed to restore: getCacheEntry failed: Cache service responded with 503
postgres16 on Linux / postgres16
Failed to restore: getCacheEntry failed: Cache service responded with 503
mssql_2022 on Linux / mssql_2022
Failed to save: reserveCache failed: Cache service responded with 503
mssql_2022 on Linux / mssql_2022
Failed to restore: getCacheEntry failed: Cache service responded with 503
mssql_2022 on Linux / mssql_2022
Failed to restore: getCacheEntry failed: Cache service responded with 503