Skip to content

chore: hardcode spec for now #1323

chore: hardcode spec for now

chore: hardcode spec for now #1323

Triggered via push August 19, 2025 13:20
Status Failure
Total duration 45s
Artifacts

pull_request.yml

on: push
Matrix: test
finish
finish
Fit to window
Zoom out
Zoom in

Annotations

37 errors, 21 warnings, and 16 notices
test (ubuntu, 3.1)
Process completed with exit code 1.
test (macos, 3.2)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (macos, 3.4)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (ubuntu, 3.3)
The operation was canceled.
test (ubuntu, 3.3)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (ubuntu, 3.4)
The operation was canceled.
test (ubuntu, 3.4)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (ubuntu, 3.0)
The operation was canceled.
test (ubuntu, 3.0)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (ubuntu, 2.7)
The operation was canceled.
test (macos, 3.1)
The operation was canceled.
test (macos, 3.1)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (ubuntu, 2.7)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (windows, 3.0)
The operation was canceled.
test (windows, 3.4)
The operation was canceled.
test (windows, 3.0)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (windows, 3.4)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (ubuntu, 3.2)
The operation was canceled.
test (ubuntu, 3.2)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (macos, 3.3)
The operation was canceled.
test (macos, 3.3)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (windows, 2.7)
The operation was canceled.
test (windows, 2.7)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (windows, 3.2)
The operation was canceled.
test (windows, 3.2)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (windows, 3.3)
The operation was canceled.
test (macos, 3.0)
The operation was canceled.
test (windows, 3.3)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (macos, 3.0)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (ubuntu, jruby-9.4)
The operation was canceled.
test (ubuntu, jruby-9.4)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (macos, jruby-9.4)
The operation was canceled.
test (macos, jruby-9.4)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (windows, 3.1)
The operation was canceled.
test (windows, 3.1)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
test (macos, 2.7)
The operation was canceled.
test (macos, 2.7)
The strategy configuration was canceled because "test.ubuntu_3_1" failed
RuboCop
The process '/usr/bin/git' failed with exit code 128
test (ubuntu, 3.1)
The process '/usr/bin/git' failed with exit code 128
test (ubuntu, 3.1)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
test (ubuntu, 3.3)
The process '/usr/bin/git' failed with exit code 128
test (ubuntu, 3.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
test (ubuntu, 3.4)
The process '/usr/bin/git' failed with exit code 128
test (ubuntu, 3.0)
The process '/usr/bin/git' failed with exit code 128
test (ubuntu, 2.7)
The process '/usr/bin/git' failed with exit code 128
test (macos, 3.1)
The process '/opt/homebrew/bin/git' failed with exit code 128
test (windows, 3.4)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
test (windows, 3.0)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
test (ubuntu, 3.2)
The process '/usr/bin/git' failed with exit code 128
test (macos, 3.3)
The process '/opt/homebrew/bin/git' failed with exit code 128
test (windows, 2.7)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
test (windows, 3.2)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
test (windows, 3.3)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
test (macos, 3.0)
The process '/opt/homebrew/bin/git' failed with exit code 128
test (ubuntu, jruby-9.4)
The process '/usr/bin/git' failed with exit code 128
test (macos, jruby-9.4)
The process '/opt/homebrew/bin/git' failed with exit code 128
test (windows, 3.1)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
test (macos, 2.7)
The process '/opt/homebrew/bin/git' failed with exit code 128
test (macos, 3.1)
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
test (macos, 3.1)
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
test (windows, 3.0)
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
test (windows, 3.4)
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
test (macos, 3.3)
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
test (macos, 3.3)
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
test (windows, 2.7)
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
test (windows, 3.2)
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
test (windows, 3.3)
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
test (macos, 3.0)
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
test (macos, 3.0)
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
test (macos, jruby-9.4)
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
test (macos, jruby-9.4)
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
test (windows, 3.1)
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
test (macos, 2.7)
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
test (macos, 2.7)
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