Skip to content

Update zig-master branch to work on Zig's master branch #114

Update zig-master branch to work on Zig's master branch

Update zig-master branch to work on Zig's master branch #114

Triggered via pull request January 20, 2025 01:26
Status Success
Total duration 46s
Artifacts

ci.yml

on: pull_request
Check that stm32 generated code is up to date
7s
Check that stm32 generated code is up to date
Build Website
10s
Build Website
Dry Run Packaging
11s
Dry Run Packaging
Matrix: Build Examples
Matrix: Build
Matrix: Unit Test Ports
Matrix: Unit Test Regz
Matrix: Unit Test UF2
Fit to window
Zoom out
Zoom in

Annotations

60 errors and 47 warnings
Build Examples (gigadevice/gd32)
Unexpected HTTP response: 404
Build Examples (gigadevice/gd32)
Unable to locate executable file: zig. 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.
Build Examples (microchip/atsam)
Unable to locate executable file: zig. 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.
Build Examples (microchip/atsam)
Unexpected HTTP response: 404
Build (ubuntu-latest)
Unexpected HTTP response: 404
Build (ubuntu-latest)
Unable to locate executable file: zig. 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.
Build Examples (espressif/esp)
Unable to locate executable file: zig. 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.
Build Examples (espressif/esp)
Unexpected HTTP response: 404
Build Examples (microchip/avr)
Unexpected HTTP response: 404
Build Examples (microchip/avr)
Unable to locate executable file: zig. 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.
Build Examples (nxp/lpc)
Unexpected HTTP response: 404
Build Examples (nxp/lpc)
Unable to locate executable file: zig. 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.
Build Examples (raspberrypi/rp2xxx)
Unexpected HTTP response: 404
Build Examples (raspberrypi/rp2xxx)
Unable to locate executable file: zig. 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 Test Ports (ubuntu-latest, raspberrypi/rp2xxx)
Unexpected HTTP response: 404
Unit Test Ports (ubuntu-latest, raspberrypi/rp2xxx)
Unable to locate executable file: zig. 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 Test Ports (ubuntu-latest, stmicro/stm32)
Unable to locate executable file: zig. 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 Test Ports (ubuntu-latest, stmicro/stm32)
Unexpected HTTP response: 404
Build Examples (nordic/nrf5x)
Unable to locate executable file: zig. 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.
Build Examples (nordic/nrf5x)
Unexpected HTTP response: 404
Build Website
Unexpected HTTP response: 404
Build Website
Unable to locate executable file: zig. 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.
Build Examples (wch/ch32v)
Unexpected HTTP response: 404
Build Examples (wch/ch32v)
Unable to locate executable file: zig. 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.
Check that stm32 generated code is up to date
Unable to locate executable file: zig. 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.
Check that stm32 generated code is up to date
Unexpected HTTP response: 404
Dry Run Packaging
Unexpected HTTP response: 404
Dry Run Packaging
Unable to locate executable file: zig. 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.
Build (macos-latest)
Unable to locate executable file: zig. 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.
Build (macos-latest)
Unexpected HTTP response: 404
Build Examples (stmicro/stm32)
Unable to locate executable file: zig. 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.
Build Examples (stmicro/stm32)
Unexpected HTTP response: 404
Unit Test Ports (macos-latest, stmicro/stm32)
Unable to locate executable file: zig. 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 Test Ports (macos-latest, stmicro/stm32)
Unexpected HTTP response: 404
Unit Test Ports (macos-latest, raspberrypi/rp2xxx)
Unable to locate executable file: zig. 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 Test Ports (macos-latest, raspberrypi/rp2xxx)
Unexpected HTTP response: 404
Unit Test Ports (macos-latest, gigadevice/gd32)
Unexpected HTTP response: 404
Unit Test Ports (macos-latest, gigadevice/gd32)
Unable to locate executable file: zig. 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.
Build (windows-latest)
Unable to locate executable file: zig. 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.
Build (windows-latest)
Unexpected HTTP response: 404
Unit Test UF2 (ubuntu-latest)
Unable to locate executable file: zig. 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 Test UF2 (ubuntu-latest)
Unexpected HTTP response: 404
Unit Test Regz (ubuntu-latest)
Unable to locate executable file: zig. 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 Test Regz (ubuntu-latest)
Unexpected HTTP response: 404
Unit Test Ports (ubuntu-latest, gigadevice/gd32)
Unexpected HTTP response: 404
Unit Test Ports (ubuntu-latest, gigadevice/gd32)
Unable to locate executable file: zig. 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 Test UF2 (macos-latest)
Unexpected HTTP response: 404
Unit Test UF2 (macos-latest)
Unable to locate executable file: zig. 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 Test Regz (macos-latest)
Unable to locate executable file: zig. 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 Test Regz (macos-latest)
Unexpected HTTP response: 404
Unit Test Regz (windows-latest)
Unable to locate executable file: zig. 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 Test Regz (windows-latest)
Unexpected HTTP response: 404
Unit Test Ports (windows-latest, gigadevice/gd32)
Unexpected HTTP response: 404
Unit Test Ports (windows-latest, gigadevice/gd32)
Unable to locate executable file: zig. 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 Test Ports (windows-latest, raspberrypi/rp2xxx)
Unexpected HTTP response: 404
Unit Test Ports (windows-latest, raspberrypi/rp2xxx)
Unable to locate executable file: zig. 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 Test UF2 (windows-latest)
Unexpected HTTP response: 404
Unit Test UF2 (windows-latest)
Unable to locate executable file: zig. 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 Test Ports (windows-latest, stmicro/stm32)
Unable to locate executable file: zig. 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 Test Ports (windows-latest, stmicro/stm32)
Unexpected HTTP response: 404
Build Examples (gigadevice/gd32)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Examples (gigadevice/gd32)
The process '/usr/bin/git' failed with exit code 128
Build Examples (microchip/atsam)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Examples (microchip/atsam)
The process '/usr/bin/git' failed with exit code 128
Build (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build (ubuntu-latest)
The process '/usr/bin/git' failed with exit code 128
Build Examples (espressif/esp)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Examples (espressif/esp)
The process '/usr/bin/git' failed with exit code 128
Build Examples (microchip/avr)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Examples (microchip/avr)
The process '/usr/bin/git' failed with exit code 128
Build Examples (nxp/lpc)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Examples (nxp/lpc)
The process '/usr/bin/git' failed with exit code 128
Build Examples (raspberrypi/rp2xxx)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Examples (raspberrypi/rp2xxx)
The process '/usr/bin/git' failed with exit code 128
Unit Test Ports (ubuntu-latest, raspberrypi/rp2xxx)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Unit Test Ports (ubuntu-latest, raspberrypi/rp2xxx)
The process '/usr/bin/git' failed with exit code 128
Unit Test Ports (ubuntu-latest, stmicro/stm32)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Unit Test Ports (ubuntu-latest, stmicro/stm32)
The process '/usr/bin/git' failed with exit code 128
Build Examples (nordic/nrf5x)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Examples (nordic/nrf5x)
The process '/usr/bin/git' failed with exit code 128
Build Website
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Website
The process '/usr/bin/git' failed with exit code 128
Build Examples (wch/ch32v)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Examples (wch/ch32v)
The process '/usr/bin/git' failed with exit code 128
Check that stm32 generated code is up to date
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Check that stm32 generated code is up to date
The process '/usr/bin/git' failed with exit code 128
Dry Run Packaging
The process '/opt/homebrew/bin/git' failed with exit code 128
Build (macos-latest)
The process '/opt/homebrew/bin/git' failed with exit code 128
Build Examples (stmicro/stm32)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Examples (stmicro/stm32)
The process '/usr/bin/git' failed with exit code 128
Unit Test Ports (macos-latest, stmicro/stm32)
The process '/opt/homebrew/bin/git' failed with exit code 128
Unit Test Ports (macos-latest, raspberrypi/rp2xxx)
The process '/opt/homebrew/bin/git' failed with exit code 128
Unit Test Ports (macos-latest, gigadevice/gd32)
The process '/opt/homebrew/bin/git' failed with exit code 128
Build (windows-latest)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
Unit Test UF2 (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Unit Test UF2 (ubuntu-latest)
The process '/usr/bin/git' failed with exit code 128
Unit Test Regz (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Unit Test Regz (ubuntu-latest)
The process '/usr/bin/git' failed with exit code 128
Unit Test Ports (ubuntu-latest, gigadevice/gd32)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Unit Test Ports (ubuntu-latest, gigadevice/gd32)
The process '/usr/bin/git' failed with exit code 128
Unit Test UF2 (macos-latest)
The process '/opt/homebrew/bin/git' failed with exit code 128
Unit Test Regz (macos-latest)
The process '/opt/homebrew/bin/git' failed with exit code 128
Unit Test Regz (windows-latest)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
Unit Test Ports (windows-latest, gigadevice/gd32)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
Unit Test Ports (windows-latest, raspberrypi/rp2xxx)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
Unit Test UF2 (windows-latest)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
Unit Test Ports (windows-latest, stmicro/stm32)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128