Skip to content
CI

Fail or warn on duplicated key during generation #1144

Sign in to view logs

Fail or warn on duplicated key during generation

Fail or warn on duplicated key during generation #1144

Triggered via pull request August 23, 2025 20:01
@byrootbyroot
synchronize #841
byroot:generate-dup-keys
Status Failure
Total duration 2m 17s
Artifacts –

ci.yml

on: pull_request
ruby-versions  /  Generate Ruby versions
5s
ruby-versions / Generate Ruby versions
Ruby memcheck
1m 6s
Ruby memcheck
Matrix: host
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 10 notices
macos-14 jruby
Process completed with exit code 1.
ubuntu-latest 2.7
Process completed with exit code 1.
macos-14 2.7
Process completed with exit code 1.
macos-14 jruby-head
Process completed with exit code 1.
macos-latest truffleruby-head
Process completed with exit code 1.
ubuntu-latest jruby
Process completed with exit code 1.
ubuntu-latest jruby-9.4
Process completed with exit code 1.
ubuntu-latest jruby-head
Process completed with exit code 1.
ubuntu-latest truffleruby-head
Process completed with exit code 1.
windows-latest 2.7
Process completed with exit code 1.
macos-latest truffleruby-head
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
macos-latest truffleruby-head
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
windows-latest mswin
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
windows-latest head
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
windows-latest 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
windows-latest 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
windows-latest 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
windows-latest 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
windows-latest 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
windows-latest 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