Nightly pipeline normal session e2e tests #663
nightly-normal-session-e2e-tests.yml
on: schedule
Run high out-latency test
0s
Sync test using synthetic-network - one node catching up and then becoming necessary for consensus
0s
Sync test using synthetic-network - one node catching up
0s
Sync test using synthetic-network - into two groups and one quorum and switch quorum between them
0s
Sync test using synthetic-network - into multiple groups of two
0s
Sync test using synthetic-network - into two equal size groups with no quorum
0s
Sync test using synthetic-network - into two groups one with quorum
0s
Run high out-latency for every quorum
0s
Annotations
7 errors
Build aleph-e2e-client image / Build aleph-e2e-client
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Build aleph-e2e-client image / Build aleph-e2e-client
The operation was canceled.
|
Build chain-bootstrapper / Build chain-bootstrapper (production=true)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Build chain-bootstrapper / Build chain-bootstrapper (production=true)
The operation was canceled.
|
Build production aleph-node / Build aleph-node (production=true)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Build production aleph-node / Build aleph-node (production=true)
The operation was canceled.
|
Check nightly test suite completion
Process completed with exit code 1.
|