Skip to content

tests

tests #5870

Triggered via schedule September 1, 2025 03:23
Status Failure
Total duration 10m 55s
Artifacts

tests.yml

on: schedule
Matrix: integration tests
Matrix: unit tests
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 4 notices
integration tests (windows-latest, 3.9)
Process completed with exit code 1.
integration tests (windows-latest, 3.9)
google-github-actions/auth failed with: the GitHub Action workflow must specify exactly one of "workload_identity_provider" or "credentials_json"! If you are specifying input values via GitHub secrets, ensure the secret is being injected into the environment. By default, secrets are not passed to workflows triggered from forks, including Dependabot.
integration tests (macos-latest, 3.13)
Process completed with exit code 1.
integration tests (macos-latest, 3.13)
google-github-actions/auth failed with: the GitHub Action workflow must specify exactly one of "workload_identity_provider" or "credentials_json"! If you are specifying input values via GitHub secrets, ensure the secret is being injected into the environment. By default, secrets are not passed to workflows triggered from forks, including Dependabot.
integration tests (windows-latest, 3.13)
Process completed with exit code 1.
integration tests (windows-latest, 3.13)
google-github-actions/auth failed with: the GitHub Action workflow must specify exactly one of "workload_identity_provider" or "credentials_json"! If you are specifying input values via GitHub secrets, ensure the secret is being injected into the environment. By default, secrets are not passed to workflows triggered from forks, including Dependabot.
integration tests (macos-latest, 3.9)
Process completed with exit code 1.
integration tests (macos-latest, 3.9)
google-github-actions/auth failed with: the GitHub Action workflow must specify exactly one of "workload_identity_provider" or "credentials_json"! If you are specifying input values via GitHub secrets, ensure the secret is being injected into the environment. By default, secrets are not passed to workflows triggered from forks, including Dependabot.
unit tests (3.9)
Process completed with exit code 1.
unit tests (3.9)
google-github-actions/auth failed with: the GitHub Action workflow must specify exactly one of "workload_identity_provider" or "credentials_json"! If you are specifying input values via GitHub secrets, ensure the secret is being injected into the environment. By default, secrets are not passed to workflows triggered from forks, including Dependabot.
integration tests (ubuntu-latest, 3.13)
Process completed with exit code 1.
integration tests (ubuntu-latest, 3.13)
google-github-actions/auth failed with: the GitHub Action workflow must specify exactly one of "workload_identity_provider" or "credentials_json"! If you are specifying input values via GitHub secrets, ensure the secret is being injected into the environment. By default, secrets are not passed to workflows triggered from forks, including Dependabot.
integration tests (ubuntu-latest, 3.9)
Process completed with exit code 1.
integration tests (ubuntu-latest, 3.9)
google-github-actions/auth failed with: the GitHub Action workflow must specify exactly one of "workload_identity_provider" or "credentials_json"! If you are specifying input values via GitHub secrets, ensure the secret is being injected into the environment. By default, secrets are not passed to workflows triggered from forks, including Dependabot.
unit tests (3.13)
Process completed with exit code 1.
unit tests (3.13)
google-github-actions/auth failed with: the GitHub Action workflow must specify exactly one of "workload_identity_provider" or "credentials_json"! If you are specifying input values via GitHub secrets, ensure the secret is being injected into the environment. By default, secrets are not passed to workflows triggered from forks, including Dependabot.
integration tests (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
integration tests (macos-latest, 3.13)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
integration tests (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
integration tests (macos-latest, 3.9)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520