Skip to content
Nightly pipeline normal session e2e tests

Nightly pipeline normal session e2e tests #590

Sign in to view logs

Nightly pipeline normal session e2e tests

Nightly pipeline normal session e2e tests #590

Manually triggered December 6, 2024 15:48
@fixxxedpointfixxxedpoint
⁠ 2edb981
A0-4318_rate_limited_substrate_network-network_flooding_test
Status Failure
Total duration 1h 10m 21s
Artifacts 7

nightly-normal-session-e2e-tests.yml

on: workflow_dispatch
Build chain-bootstrapper  /  Build chain-bootstrapper (production=true)
7m 52s
Build chain-bootstrapper / Build chain-bootstrapper (production=true)
Check vars and secrets  /  Check available vars and secrets
0s
Check vars and secrets / Check available vars and secrets
Build aleph-e2e-client image  /  Build aleph-e2e-client
4m 39s
Build aleph-e2e-client image / Build aleph-e2e-client
Build production aleph-node  /  Build aleph-node (production=true)
10m 34s
Build production aleph-node / Build aleph-node (production=true)
Build aleph-node with flooding routines for both sync-network and alephbft-network  /  Build aleph-node (production=false)
27s
Build aleph-node with flooding routines for both sync-network and alephbft-network / Build aleph-node (production=false)
Build synthetic node  /  Build synthetic node docker image
1m 57s
Build synthetic node / Build synthetic node docker image
Run major sync test
58m 36s
Run major sync test
Run force reorgs test
9m 10s
Run force reorgs test
Run network flooding test
0s
Run network flooding test
Run high out-latency test
16m 36s
Run high out-latency test
Sync test using synthetic-network - one node catching up and then becoming necessary for consensus
4m 54s
Sync test using synthetic-network - one node catching up and then becoming necessary for consensus
Sync test using synthetic-network - one node catching up
9m 1s
Sync test using synthetic-network - one node catching up
Sync test using synthetic-network - into two groups and one quorum and switch quorum between them
2m 23s
Sync test using synthetic-network - into two groups and one quorum and switch quorum between them
Sync test using synthetic-network - into multiple groups of two
3m 2s
Sync test using synthetic-network - into multiple groups of two
Sync test using synthetic-network - into two equal size groups with no quorum
3m 34s
Sync test using synthetic-network - into two equal size groups with no quorum
Sync test using synthetic-network - into two groups one with quorum
2m 39s
Sync test using synthetic-network - into two groups one with quorum
Run high out-latency for every quorum
16m 30s
Run high out-latency for every quorum
Finalization-stall test using synthetic-network
44m 58s
Finalization-stall test using synthetic-network
Check nightly test suite completion
0s
Check nightly test suite completion
Slack notification
0s
Slack notification
Fit to window
Zoom out
Zoom in

Annotations

5 errors
Build aleph-node with flooding routines for both sync-network and alephbft-network / Build aleph-node (production=false)
Build aleph-node with flooding routines for both sync-network and alephbft-network / Build aleph-node (production=false)
Build aleph-node with flooding routines for both sync-network and alephbft-network / Build aleph-node (production=false)
Build aleph-node with flooding routines for both sync-network and alephbft-network / Build aleph-node (production=false)
The process '/usr/bin/git' failed with exit code 128
Check nightly test suite completion
Process completed with exit code 1.

Artifacts

Produced during runtime
Name Size
aleph-e2e-client Expired
5.86 MB
aleph-e2e-client-image Expired
73.3 MB
aleph-node-image-production Expired
53.3 MB
aleph-node-production Expired
21.7 MB
aleph-release-synthetic-docker Expired
221 MB
chain-bootstrapper-image-release Expired
76.9 MB
chain-bootstrapper-release Expired
7.79 MB