Skip to content

fix: properly detect, specify, and handle connecting forked network to non-fork [APE-1393] #692

fix: properly detect, specify, and handle connecting forked network to non-fork [APE-1393]

fix: properly detect, specify, and handle connecting forked network to non-fork [APE-1393] #692

Triggered via pull request September 14, 2023 21:49
Status Failure
Total duration 3m 57s
Artifacts

test.yaml

on: pull_request
Matrix: functional
Fit to window
Zoom out
Zoom in

Annotations

15 errors
functional (3.10, ubuntu-latest)
Process completed with exit code 1.
functional (3.8, ubuntu-latest)
The job was canceled because "_3_10_ubuntu-latest" failed.
functional (3.8, ubuntu-latest)
The operation was canceled.
functional (3.11, ubuntu-latest)
The job was canceled because "_3_10_ubuntu-latest" failed.
functional (3.11, ubuntu-latest)
The operation was canceled.
functional (3.8, macos-latest)
The job was canceled because "_3_10_ubuntu-latest" failed.
functional (3.8, macos-latest)
The operation was canceled.
functional (3.9, macos-latest)
The job was canceled because "_3_10_ubuntu-latest" failed.
functional (3.9, macos-latest)
The operation was canceled.
functional (3.9, ubuntu-latest)
The job was canceled because "_3_10_ubuntu-latest" failed.
functional (3.9, ubuntu-latest)
The operation was canceled.
functional (3.11, macos-latest)
The job was canceled because "_3_10_ubuntu-latest" failed.
functional (3.11, macos-latest)
The operation was canceled.
functional (3.10, macos-latest)
The job was canceled because "_3_10_ubuntu-latest" failed.
functional (3.10, macos-latest)
The operation was canceled.