Skip to content
Build and Release

Handle missing native exports when running tests #60

Sign in to view logs

Handle missing native exports when running tests

Handle missing native exports when running tests #60

Triggered via pull request October 25, 2025 17:42
@KSemenenkoKSemenenko
synchronize #9
codex/integrate-mlx-lm-with-.net-framework-6lysso
Status Failure
Total duration 1m 38s
Artifacts 3

ci.yml

on: pull_request
dotnet-build
20s
dotnet-build
native-assets
15s
native-assets
package-test
44s
package-test
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
package-test
Process completed with exit code 1.
package-test
Resolved metallib via recursive search under /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/mlx
package-test
mlx.metallib missing from native artifact; attempting to source from installed mlx package

Artifacts

Produced during runtime
Name Size Digest
native-linux-x64
3.62 KB
sha256:c72d0dc15b8ee4625fc5fd16aaaeacb87704e46765289c5eb7e86c658a0464b5
native-osx-arm64
2.02 KB
sha256:38aefa15d2dbee65beb04f253da7dd7e187f8a9f6f1a60ac2f0df4c40354a2b9
test-results
2.02 KB
sha256:9d46eda0778803554d8c93175a2951650b06ebb15b24d78373ffb323e17d1492