Skip to content

fruity: Fix teardown when using our NCM driver #368

fruity: Fix teardown when using our NCM driver

fruity: Fix teardown when using our NCM driver #368

Triggered via push September 17, 2024 16:34
Status Failure
Total duration 1d 2h 9m 13s
Artifacts 16

ci.yml

on: push
Matrix: cross
Matrix: manylinux
Matrix: mobile
Matrix: native
Fit to window
Zoom out
Zoom in

Annotations

10 errors
mobile (android-x86)
Process completed with exit code 1.
mobile (android-arm)
Process completed with exit code 1.
mobile (android-arm64)
Process completed with exit code 1.
mobile (android-x86_64)
Process completed with exit code 1.
mobile (ios-arm64)
Request failed: Bad Gateway
native (windows-x86, "windows-latest")
Process completed with exit code 1.
native (windows-x86_64, "windows-latest")
Process completed with exit code 1.
native (freebsd-arm64, ["self-hosted", "freebsd", "arm64"])
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.

Artifacts

Produced during runtime
Name Size
core-devkit-ios-arm64
52.4 MB
core-devkit-linux-arm64
64.5 MB
core-devkit-linux-arm64-musl
63.1 MB
core-devkit-linux-armhf
52.8 MB
core-devkit-linux-mips
51.5 MB
core-devkit-linux-mips64
64.1 MB
core-devkit-linux-mips64el
61 MB
core-devkit-linux-mipsel
49.6 MB
core-devkit-linux-x86
49.8 MB
core-devkit-linux-x86_64
78.7 MB
core-devkit-linux-x86_64-musl
62.2 MB
core-devkit-macos-arm64
64.8 MB
core-devkit-macos-x86_64
64.8 MB
core-devkit-qnx-armeabi
44.4 MB
core-devkit-windows-x86
86.6 MB
core-devkit-windows-x86_64
86.6 MB