Skip to content
Backwards Compatibility Unit Tests

Skip migrations check for backwards compatibility tests #385

Sign in to view logs

Skip migrations check for backwards compatibility tests

Skip migrations check for backwards compatibility tests #385

Triggered via pull request April 3, 2025 13:03
@philippthunphilippthun
synchronize #4294
sap-contributions:skip-migrations-check-for-backwards-compatibility-tests
Status Failure
Total duration 30m 25s
Artifacts –

unit_tests_backwards_compatibility.yml

on: pull_request
Matrix: Test-Mysql-Backwards-Compatibillity
Matrix: Test-Postgres-Backwards-Compatibillity
Fit to window
Zoom out
Zoom in

Annotations

12 errors
Test-Mysql-Backwards-Compatibillity (mysql:8.2)
The job running on runner GitHub Actions 413 has exceeded the maximum execution time of 30 minutes.
Test-Mysql-Backwards-Compatibillity (mysql:8.2)
The operation was canceled.
Test-Postgres-Backwards-Compatibillity (postgres:13)
The job running on runner GitHub Actions 374 has exceeded the maximum execution time of 30 minutes.
Test-Postgres-Backwards-Compatibillity (postgres:13)
The operation was canceled.
Test-Postgres-Backwards-Compatibillity (postgres:15)
The job running on runner GitHub Actions 371 has exceeded the maximum execution time of 30 minutes.
Test-Postgres-Backwards-Compatibillity (postgres:15)
The operation was canceled.
Test-Postgres-Backwards-Compatibillity (postgres:16)
The job running on runner GitHub Actions 300 has exceeded the maximum execution time of 30 minutes.
Test-Postgres-Backwards-Compatibillity (postgres:16)
The operation was canceled.
Test-Mysql-Backwards-Compatibillity (mysql:5.7)
The job running on runner GitHub Actions 168 has exceeded the maximum execution time of 30 minutes.
Test-Mysql-Backwards-Compatibillity (mysql:5.7)
The operation was canceled.
Test-Mysql-Backwards-Compatibillity (mysql:8.0)
The job running on runner GitHub Actions 197 has exceeded the maximum execution time of 30 minutes.
Test-Mysql-Backwards-Compatibillity (mysql:8.0)
The operation was canceled.