Skip to content

Fix a workflow bug where a non-jit run could use a jit cached beam #5729

Fix a workflow bug where a non-jit run could use a jit cached beam

Fix a workflow bug where a non-jit run could use a jit cached beam #5729

Triggered via pull request February 17, 2026 14:09
Status Success
Total duration 1h 33m 53s
Artifacts

run-tests-with-beam.yaml

on: pull_request
Matrix: run-tests
Fit to window
Zoom out
Zoom in

Annotations

1 error
run-tests (ubuntu-24.04, -s prime_smp, erlang:21, 21, true)
the remote end hung up unexpectedly