Skip to content

Update jerryscript to 3.0.0 #12

Update jerryscript to 3.0.0

Update jerryscript to 3.0.0 #12

Triggered via pull request September 14, 2025 09:42
Status Failure
Total duration 7m 5s
Artifacts

ci-push.yml

on: pull_request
Matrix: build / build
Fit to window
Zoom out
Zoom in

Annotations

26 errors, 8 warnings, and 8 notices
build / build (macos-latest, host, gcc)
Process completed with exit code 2.
build / build (macos-latest, rp2040, gcc)
Process completed with exit code 2.
build / build (windows-latest, host, gcc)
Process completed with exit code 1.
build / build (windows-latest, esp8266, gcc)
Process completed with exit code 1.
build / build (windows-latest, rp2040, gcc)
Process completed with exit code 1.
build / build (macos-latest, esp8266, gcc)
Process completed with exit code 2.
build / build (ubuntu-latest, rp2040, gcc)
Process completed with exit code 2.
build / build (ubuntu-latest, host, gcc)
Process completed with exit code 2.
build / build (ubuntu-latest, host, gcc64, Host)
Process completed with exit code 2.
build / build (ubuntu-latest, esp8266, gcc)
Process completed with exit code 2.
build / build (ubuntu-latest, host, clang, Host)
Process completed with exit code 2.
build / build (ubuntu-latest, esp32c3, gcc)
Process completed with exit code 2.
build / build (macos-latest, esp32, gcc)
Process completed with exit code 2.
build / build (ubuntu-latest, esp32c2, gcc)
Process completed with exit code 2.
build / build (macos-latest, esp32s3, gcc)
Process completed with exit code 2.
build / build (ubuntu-latest, esp32s2, gcc)
Process completed with exit code 2.
build / build (ubuntu-latest, esp32, gcc)
Process completed with exit code 2.
build / build (ubuntu-latest, esp32s3, gcc)
Process completed with exit code 2.
build / build (macos-latest, esp32c2, gcc)
Process completed with exit code 2.
build / build (windows-latest, esp32s2, gcc)
Process completed with exit code 1.
build / build (windows-latest, esp32c2, gcc)
Process completed with exit code 1.
build / build (macos-latest, esp32c3, gcc)
Process completed with exit code 2.
build / build (windows-latest, esp32c3, gcc)
Process completed with exit code 1.
build / build (windows-latest, esp32s3, gcc)
Process completed with exit code 1.
build / build (windows-latest, esp32, gcc)
Process completed with exit code 1.
build / build (macos-latest, esp32s2, gcc)
Process completed with exit code 2.
build / build (macos-latest, host, gcc)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
build / build (macos-latest, rp2040, gcc)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
build / build (macos-latest, esp8266, gcc)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
build / build (macos-latest, esp32, gcc)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
build / build (macos-latest, esp32s3, gcc)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
build / build (macos-latest, esp32c2, gcc)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
build / build (macos-latest, esp32c3, gcc)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
build / build (macos-latest, esp32s2, gcc)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
build / build (windows-latest, host, gcc)
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
build / build (windows-latest, esp8266, gcc)
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
build / build (windows-latest, rp2040, gcc)
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
build / build (windows-latest, esp32s2, gcc)
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
build / build (windows-latest, esp32c2, gcc)
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
build / build (windows-latest, esp32c3, gcc)
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
build / build (windows-latest, esp32s3, gcc)
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
build / build (windows-latest, esp32, gcc)
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