Skip to content

haxeui-core push: Merge remote-tracking branch 'origin/master' #2111

haxeui-core push: Merge remote-tracking branch 'origin/master'

haxeui-core push: Merge remote-tracking branch 'origin/master' #2111

Triggered via repository dispatch November 22, 2024 11:30
@ianharriganianharrigan
haxeui-core push: Merge remote-tracking branch 'origin/master' 4739ec1
Status Failure
Total duration 9m 16s
Artifacts

build.yml

on: repository_dispatch
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 1 warning
build (windows-latest, 4.0.5)
Process completed with exit code 1.
build (ubuntu-latest, 4.1.5)
The job was canceled because "windows-latest_4_0_5" failed.
build (macos-13, 4.2.2)
The job was canceled because "windows-latest_4_0_5" failed.
build (macos-13, 4.0.5)
The job was canceled because "windows-latest_4_0_5" failed.
build (macos-13, 4.3.1)
The job was canceled because "windows-latest_4_0_5" failed.
build (ubuntu-latest, 4.2.2)
The job was canceled because "windows-latest_4_0_5" failed.
build (macos-13, 4.3.0)
The job was canceled because "windows-latest_4_0_5" failed.
build (macos-13, 4.1.5)
The job was canceled because "windows-latest_4_0_5" failed.
build (ubuntu-latest, 4.0.5)
The job was canceled because "windows-latest_4_0_5" failed.
build (ubuntu-latest, 4.3.1)
The job was canceled because "windows-latest_4_0_5" failed.
build (ubuntu-latest, 4.3.0)
The job was canceled because "windows-latest_4_0_5" failed.
build (windows-latest, 4.2.2)
The job was canceled because "windows-latest_4_0_5" failed.
build (windows-latest, 4.1.5)
The job was canceled because "windows-latest_4_0_5" failed.
build (windows-latest, 4.3.1)
The job was canceled because "windows-latest_4_0_5" failed.
build (windows-latest, 4.3.0)
The job was canceled because "windows-latest_4_0_5" failed.
build (windows-latest, 4.0.5)
The following actions use a deprecated Node.js version and will be forced to run on node20: krdlab/setup-haxe@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/