Skip to content
Latest ORM 6.2.x

Revert "[#1791] Upgrade Vert.x SQL client to 4.5.0" #14

Sign in to view logs

Revert "[#1791] Upgrade Vert.x SQL client to 4.5.0"

Revert "[#1791] Upgrade Vert.x SQL client to 4.5.0" #14

Triggered via pull request January 12, 2024 10:49
@DavideDDavideD
synchronize #1830
DavideD:revert-vertx
Status Failure
Total duration 4m 26s
Artifacts –

tracking-orm-6.2.build.yml

on: pull_request
Matrix: run_examples
Matrix: test_dbs
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 10 warnings
Test with PostgreSQL and ORM [6.2,6.3)
Process completed with exit code 1.
Test with MariaDB and ORM [6.2,6.3)
Process completed with exit code 1.
Test with MySQL and ORM [6.2,6.3)
The operation was canceled.
Test with CockroachDB and ORM [6.2,6.3)
The operation was canceled.
Test with Oracle and ORM [6.2,6.3)
The operation was canceled.
Test with MSSQLServer and ORM [6.2,6.3)
The operation was canceled.
Test with DB2 and ORM [6.2,6.3)
The operation was canceled.
Run examples in 'native-sql-example' on PostgreSQL with latest ORM [6.2,6.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run examples in 'session-example' on MySQL with latest ORM [6.2,6.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run examples in 'session-example' on PostgreSQL with latest ORM [6.2,6.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test with PostgreSQL and ORM [6.2,6.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test with MariaDB and ORM [6.2,6.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test with MySQL and ORM [6.2,6.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test with CockroachDB and ORM [6.2,6.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test with Oracle and ORM [6.2,6.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test with MSSQLServer and ORM [6.2,6.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test with DB2 and ORM [6.2,6.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/