Skip to content
Exotic builds testing

Revert "assertions" #2037

Sign in to view logs

Revert "assertions"

Revert "assertions" #2037

Triggered via push January 17, 2025 14:42
@ligurioligurio
pushed 01c2c57
ligurio/lj-1087-vm-handler-call
Status Failure
Total duration 40m 46s
Artifacts –

exotic-builds-testing.yml

on: push
Matrix: test-exotic
Fit to window
Zoom out
Zoom in

Annotations

10 errors
LuaJIT nojit (Linux/x86_64) Debug GC64:OFF
Process completed with exit code 1.
LuaJIT nojit (Linux/x86_64) Debug GC64:ON
Process completed with exit code 1.
LuaJIT checkhook (Linux/ARM64) Debug GC64:ON
The self-hosted runner: vds5 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
LuaJIT nojit (Linux/ARM64) Debug GC64:ON
The self-hosted runner: vds1 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
LuaJIT gdbjit (Linux/ARM64) Debug GC64:ON
The self-hosted runner: vds3 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
LuaJIT gdbjit (Linux/ARM64) Release GC64:ON
The self-hosted runner: vds5 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
LuaJIT nounwind (Linux/ARM64) Debug GC64:ON
The self-hosted runner: vds3 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
LuaJIT checkhook (Linux/ARM64) Release GC64:ON
The self-hosted runner: vds1 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
LuaJIT nojit (Linux/ARM64) Release GC64:ON
The self-hosted runner: vds3 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
LuaJIT nounwind (Linux/ARM64) Release GC64:ON
The self-hosted runner: vds5 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.