Skip to content

Use batch database operations instead of one by one to optimze api pulls #24292

Use batch database operations instead of one by one to optimze api pulls

Use batch database operations instead of one by one to optimze api pulls #24292

Triggered via pull request December 10, 2024 19:59
Status Cancelled
Total duration 1m 17s
Artifacts

pull-e2e-tests.yml

on: pull_request
files-changed  /  detect
5s
files-changed / detect
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
test-e2e
Canceling since a higher priority waiting request for 'e2e-tests-lunny/pull_requests_api' exists
test-e2e
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