Skip to content

[stable35] chore(deps): Update openapi-extractor to v1.9.1 #55028

[stable35] chore(deps): Update openapi-extractor to v1.9.1

[stable35] chore(deps): Update openapi-extractor to v1.9.1 #55028

Triggered via pull request September 2, 2026 12:55
Status Failure
Total duration 1h 56m 48s
Artifacts

integration-sqlite.yml

on: pull_request
changes
8s
changes
Matrix: integration-sqlite
integration-sqlite-summary
8s
integration-sqlite-summary
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 20 warnings
integration-sqlite (federation_features, 8.5, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1
integration-sqlite (ldap_features, 8.5, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1
integration-sqlite (collaboration_features, 8.5, main, stable35, stable35)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
integration-sqlite (federation_features, 8.3, main, stable35, stable35)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
integration-sqlite (openldap_numerical_features, 8.5, main, stable35, stable35)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
integration-sqlite (setup_features, 8.5, main, stable35, stable35)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
integration-sqlite (sharing_features, 8.5, main, stable35, stable35)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
integration-sqlite (theming_features, 8.3, main, stable35, stable35)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
integration-sqlite-summary
Process completed with exit code 1.
integration-sqlite (federation_features, 8.5, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 7.556 seconds before retry.
integration-sqlite (federation_features, 8.5, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 4.02 seconds before retry.
integration-sqlite (file_conversions, 8.5, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 2.648 seconds before retry.
integration-sqlite (file_conversions, 8.5, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 4.236 seconds before retry.
integration-sqlite (collaboration_features, 8.3, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 3.676 seconds before retry.
integration-sqlite (collaboration_features, 8.3, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 3.219 seconds before retry.
integration-sqlite (collaboration_features, 8.3, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 5.712 seconds before retry.
integration-sqlite (ldap_features, 8.5, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 6.939 seconds before retry.
integration-sqlite (ldap_features, 8.5, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 2.171 seconds before retry.
integration-sqlite (ldap_features, 8.5, main, stable35, stable35)
Docker pull failed with exit code 1, back off 1.796 seconds before retry.
integration-sqlite (ldap_features, 8.5, main, stable35, stable35)
Docker pull failed with exit code 1, back off 4.243 seconds before retry.
integration-sqlite (file_conversions, 8.3, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 2.975 seconds before retry.
integration-sqlite (file_conversions, 8.3, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 2.694 seconds before retry.
integration-sqlite (videoverification_features, 8.5, main, stable35, stable35)
Docker pull failed with exit code 1, back off 1.093 seconds before retry.
integration-sqlite (sharees_features, 8.5, main, stable35, stable35)
Docker pull failed with exit code 1, back off 7.942 seconds before retry.
integration-sqlite (sharees_features, 8.5, main, stable35, stable35)
Docker pull failed with exit code 1, back off 9.828 seconds before retry.
integration-sqlite (videoverification_features, 8.3, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 5.094 seconds before retry.
integration-sqlite (--tags ~@requires-s3 dav_features, 8.5, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 5.305 seconds before retry.
integration-sqlite (ldap_features, 8.3, main, stable35, stable35)
Docker login for 'ghcr.io' failed with exit code 1, back off 9.705 seconds before retry.
integration-sqlite (sharing_features, 8.3, main, stable35, stable35)
Docker pull failed with exit code 1, back off 7.326 seconds before retry.