Skip to content
CI/CD Pipeline

fix: rename max variable to avoid built-in function conflict #8

Sign in to view logs

fix: rename max variable to avoid built-in function conflict

fix: rename max variable to avoid built-in function conflict #8

Triggered via push September 28, 2025 13:00
@Cod-e-CodesCod-e-Codes
pushed 9a73b53
main
Status Failure
Total duration 2m 45s
Artifacts 2

ci.yml

on: push
Test
1m 12s
Test
Matrix: Build
Release
0s
Release
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 1 notice
Build (ubuntu-latest, linux, arm64)
Process completed with exit code 1.
Build (ubuntu-latest, linux, arm64)
undefined: newContext
Build (ubuntu-latest, linux, arm64)
undefined: context
Build (windows-latest, windows, amd64, .exe)
The operation was canceled.
Build (windows-latest, windows, amd64, .exe)
The strategy configuration was canceled because "build.ubuntu-latest_linux_arm64" failed
Build (ubuntu-latest, linux, amd64)
The operation was canceled.
Build (ubuntu-latest, linux, amd64)
The strategy configuration was canceled because "build.ubuntu-latest_linux_arm64" failed
Build (windows-latest, windows, amd64, .exe)
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

Artifacts

Produced during runtime
Name Size Digest
tuitar-darwin-amd64 Expired
3.26 MB
sha256:2ec2cda921d591ffe26dd6a6ae1736b0f6a60903304fd6a3b678071e5e92d043
tuitar-darwin-arm64 Expired
3.13 MB
sha256:c184d322a150e7ae15bd7b0bbe8e41608ccb9214feb91cb8813cfe5285f965d3