Use batch database operations instead of one by one to optimze api pulls #24288
Triggered via pull request
December 10, 2024 19:59
lunny
Status
Cancelled
Total duration
1m 20s
Artifacts
–
pull-db-tests.yml
on: pull_request
files-changed
/
detect
5s
test-pgsql
55s
test-sqlite
50s
test-unit
38s
test-mysql
38s
test-mssql
45s
Annotations
10 errors and 1 warning
|
test-unit
Canceling since a higher priority waiting request for 'db-tests-lunny/pull_requests_api' exists
|
|
test-unit
The operation was canceled.
|
|
test-mysql
Canceling since a higher priority waiting request for 'db-tests-lunny/pull_requests_api' exists
|
|
test-mysql
The operation was canceled.
|
|
test-mssql
Canceling since a higher priority waiting request for 'db-tests-lunny/pull_requests_api' exists
|
|
test-mssql
The operation was canceled.
|
|
test-sqlite
Canceling since a higher priority waiting request for 'db-tests-lunny/pull_requests_api' exists
|
|
test-sqlite
The operation was canceled.
|
|
test-pgsql
Canceling since a higher priority waiting request for 'db-tests-lunny/pull_requests_api' exists
|
|
test-pgsql
The operation was canceled.
|
|
files-changed / detect
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|