Skip to content
GAP

Fix incorrect OutNeighbours usage #37

Sign in to view logs

Fix incorrect OutNeighbours usage

Fix incorrect OutNeighbours usage #37

Triggered via push February 6, 2024 15:38
@DanielPointonDanielPointon
pushed 4166869
main
Status Failure
Total duration 4h 2m 4s
Artifacts –

gap.yml

on: push
cygwin / GAP master
49m 0s
cygwin / GAP master
with-external-planarity-bliss
59m 56s
with-external-planarity-bliss
Matrix: test-unix
Fit to window
Zoom out
Zoom in

Annotations

12 errors
ubuntu32 / GAP master
Process completed with exit code 1.
ubuntu / GAP stable-4.11
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
ubuntu / GAP stable-4.11
The operation was canceled.
ubuntu / GAP stable-4.10
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
ubuntu / GAP stable-4.10
The operation was canceled.
ubuntu / GAP stable-4.12
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
ubuntu / GAP stable-4.12
The operation was canceled.
ubuntu / GAP master
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
ubuntu / GAP master
The operation was canceled.
cygwin / GAP master
Process completed with exit code 138.
with-external-planarity-bliss
The hosted runner: GitHub Actions 20 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
macos / GAP master
Process completed with exit code 137.