Skip to content

test commit

test commit #23

Triggered via push August 20, 2025 14:41
Status Failure
Total duration 8m 29s
Artifacts

test.yml

on: push
GitHub Integration Tests
32s
GitHub Integration Tests
Bitbucket Server Integration Tests
1m 26s
Bitbucket Server Integration Tests
Matrix: Azure Integration Tests
Matrix: GitLab Integration Tests
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

99 errors, 48 warnings, and 13 notices
Pretest
Cannot open: File exists
Pretest
Cannot open: File exists
Pretest
Cannot open: File exists
Pretest
Cannot open: File exists
Pretest
Cannot open: File exists
Pretest
Cannot open: File exists
Pretest
Cannot open: File exists
Pretest
Cannot open: File exists
Pretest
Cannot open: File exists
Pretest
Cannot open: File exists
Scan Repository Tests (ubuntu)
Process completed with exit code 1.
Scan Repository Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (ubuntu)
Process completed with exit code 1.
Scan Pull Request Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (macos)
Process completed with exit code 1.
Scan Repository Tests (macos)
Cannot open: File exists
Scan Repository Tests (macos)
Cannot open: File exists
Scan Repository Tests (macos)
Cannot open: File exists
Scan Repository Tests (macos)
Cannot open: File exists
Scan Repository Tests (macos)
Cannot open: File exists
Scan Repository Tests (macos)
Cannot open: File exists
Scan Repository Tests (macos)
Cannot open: File exists
Scan Repository Tests (macos)
Cannot open: File exists
Scan Repository Tests (macos)
Cannot open: File exists
Scan Repository Tests (macos)
Cannot open: File exists
Unit Tests (ubuntu)
Cannot open: File exists
Unit Tests (ubuntu)
Cannot open: File exists
Unit Tests (ubuntu)
Cannot open: File exists
Unit Tests (ubuntu)
Cannot open: File exists
Unit Tests (ubuntu)
Cannot open: File exists
Unit Tests (ubuntu)
Cannot open: File exists
Unit Tests (ubuntu)
Cannot open: File exists
Unit Tests (ubuntu)
Cannot open: File exists
Unit Tests (ubuntu)
Cannot open: File exists
Unit Tests (ubuntu)
Cannot open: File exists
Scan Pull Request Tests (macos)
Process completed with exit code 1.
Scan Pull Request Tests (macos)
Cannot open: File exists
Scan Pull Request Tests (macos)
Cannot open: File exists
Scan Pull Request Tests (macos)
Cannot open: File exists
Scan Pull Request Tests (macos)
Cannot open: File exists
Scan Pull Request Tests (macos)
Cannot open: File exists
Scan Pull Request Tests (macos)
Cannot open: File exists
Scan Pull Request Tests (macos)
Cannot open: File exists
Scan Pull Request Tests (macos)
Cannot open: File exists
Scan Pull Request Tests (macos)
Cannot open: File exists
Scan Pull Request Tests (macos)
Cannot open: File exists
Unit Tests (macos)
Cannot open: File exists
Unit Tests (macos)
Cannot open: File exists
Unit Tests (macos)
Cannot open: File exists
Unit Tests (macos)
Cannot open: File exists
Unit Tests (macos)
Cannot open: File exists
Unit Tests (macos)
Cannot open: File exists
Unit Tests (macos)
Cannot open: File exists
Unit Tests (macos)
Cannot open: File exists
Unit Tests (macos)
Cannot open: File exists
Unit Tests (macos)
Cannot open: File exists
Package Handlers Tests (ubuntu)
Process completed with exit code 1.
Package Handlers Tests (ubuntu)
Cannot open: File exists
Package Handlers Tests (ubuntu)
Cannot open: File exists
Package Handlers Tests (ubuntu)
Cannot open: File exists
Package Handlers Tests (ubuntu)
Cannot open: File exists
Package Handlers Tests (ubuntu)
Cannot open: File exists
Package Handlers Tests (ubuntu)
Cannot open: File exists
Package Handlers Tests (ubuntu)
Cannot open: File exists
Package Handlers Tests (ubuntu)
Cannot open: File exists
Package Handlers Tests (ubuntu)
Cannot open: File exists
Package Handlers Tests (ubuntu)
Cannot open: File exists
Scan Repository Tests (windows)
Process completed with exit code 1.
Scan Pull Request Tests (windows)
Process completed with exit code 1.
Package Handlers Tests (macos)
Process completed with exit code 1.
Package Handlers Tests (macos)
Cannot open: File exists
Package Handlers Tests (macos)
Cannot open: File exists
Package Handlers Tests (macos)
Cannot open: File exists
Package Handlers Tests (macos)
Cannot open: File exists
Package Handlers Tests (macos)
Cannot open: File exists
Package Handlers Tests (macos)
Cannot open: File exists
Package Handlers Tests (macos)
Cannot open: File exists
Package Handlers Tests (macos)
Cannot open: File exists
Package Handlers Tests (macos)
Cannot open: File exists
Package Handlers Tests (macos)
Cannot open: File exists
Package Handlers Tests (windows)
Process completed with exit code 1.
Pretest
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
GitLab Integration Tests (macos)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
GitLab Integration Tests (macos)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
GitLab Integration Tests (macos)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Azure Integration Tests (macos)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Azure Integration Tests (macos)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Azure Integration Tests (macos)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Bitbucket Server Integration Tests
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Bitbucket Server Integration Tests
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Bitbucket Server Integration Tests
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Scan Repository Tests (ubuntu)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
Scan Pull Request Tests (ubuntu)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
GitLab Integration Tests (windows)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
GitLab Integration Tests (windows)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
GitLab Integration Tests (windows)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Scan Repository Tests (macos)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Scan Repository Tests (macos)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Scan Repository Tests (macos)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Scan Repository Tests (macos)
Failed to restore: "/opt/homebrew/bin/gtar" failed with error: The process '/opt/homebrew/bin/gtar' failed with exit code 2
Azure Integration Tests (windows)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Azure Integration Tests (windows)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Azure Integration Tests (windows)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Unit Tests (ubuntu)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
Scan Pull Request Tests (macos)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Scan Pull Request Tests (macos)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Scan Pull Request Tests (macos)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Scan Pull Request Tests (macos)
Failed to restore: "/opt/homebrew/bin/gtar" failed with error: The process '/opt/homebrew/bin/gtar' failed with exit code 2
Unit Tests (macos)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Unit Tests (macos)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Unit Tests (macos)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Unit Tests (macos)
Failed to restore: "/opt/homebrew/bin/gtar" failed with error: The process '/opt/homebrew/bin/gtar' failed with exit code 2
Package Handlers Tests (ubuntu)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
Scan Repository Tests (windows)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Scan Repository Tests (windows)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Scan Repository Tests (windows)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Scan Pull Request Tests (windows)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Scan Pull Request Tests (windows)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Scan Pull Request Tests (windows)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Package Handlers Tests (macos)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Package Handlers Tests (macos)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Package Handlers Tests (macos)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-arm64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Package Handlers Tests (macos)
Failed to restore: "/opt/homebrew/bin/gtar" failed with error: The process '/opt/homebrew/bin/gtar' failed with exit code 2
Unit Tests (windows)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Unit Tests (windows)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Unit Tests (windows)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Package Handlers Tests (windows)
export-otel failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Package Handlers Tests (windows)
store-cache failed: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Package Handlers Tests (windows)
Failed to store cache: Error: Unable to locate executable file: /tmp/fastci/tools/bashi-amd64. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
GitLab Integration Tests (macos)
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
Azure Integration Tests (macos)
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
Bitbucket Server Integration Tests
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
GitLab Integration Tests (windows)
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
Scan Repository Tests (macos)
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
Azure Integration Tests (windows)
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
Scan Pull Request Tests (macos)
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
Unit Tests (macos)
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
Scan Repository Tests (windows)
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
Scan Pull Request Tests (windows)
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
Package Handlers Tests (macos)
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
Unit Tests (windows)
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
Package Handlers Tests (windows)
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