Skip to content

Using pip instead of gh CLI in the migration tests #3925

Using pip instead of gh CLI in the migration tests

Using pip instead of gh CLI in the migration tests #3925

Re-run triggered October 24, 2024 10:45
Status Cancelled
Total duration 3h 17m 15s
Artifacts

ci-slow.yml

on: pull_request
run-slow-ci-label-is-set
4s
run-slow-ci-label-is-set
docstring-check
14m 39s
docstring-check
mysql-db-migration-testing-full
1h 8m
mysql-db-migration-testing-full
mysql-db-migration-testing-random
18m 17s
mysql-db-migration-testing-random
sqlite-db-migration-testing-full
45m 20s
sqlite-db-migration-testing-full
mariadb-db-migration-testing
1h 10m
mariadb-db-migration-testing
small-checks
8m 58s
small-checks
Matrix: custom-ubuntu-integration-test
Matrix: custom-ubuntu-unit-test
Matrix: macos-integration-test
Matrix: macos-unit-test
Matrix: windows-integration-test
Matrix: windows-unit-test
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
run-slow-ci-label-is-set
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@v5. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
run-slow-ci-label-is-set
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/github-script@v5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/