Skip to content
Continuous Integration

Stress tests with redis-encoded test plans #6627

Sign in to view logs

Stress tests with redis-encoded test plans

Stress tests with redis-encoded test plans #6627

Triggered via pull request October 17, 2024 16:03
@clemireclemire
synchronize #1280
crystal/stress-test-commands
Status Failure
Total duration 26m 38s
Billable time 1h 5m
Artifacts 3

ci.yml

on: pull_request
Common_CI
8m 21s
Common_CI
Multinode
14m 0s
Multinode
Multinode_Ent
25m 0s
Multinode_Ent
Go_Tests
5m 56s
Go_Tests
XChain_Integration
2m 48s
XChain_Integration
Multinode_Ent_Legacy
7m 34s
Multinode_Ent_Legacy
Slack_Notification
5s
Slack_Notification
Fit to window
Zoom out
Zoom in

Annotations

6 errors
Multinode_Ent_Legacy
@river-build/web3#test:ci: command (/home/runner/work/river/river/packages/web3) /tmp/xfs-bb85af5f/yarn run test:ci exited (1)
Multinode_Ent_Legacy
Process completed with exit code 1.
Common_CI: packages/stress/src/mode/chat/schema/executeCommand.ts#L56
Forbidden non-null assertion
Common_CI
@river-build/stress#lint: command (/home/runner/work/river/river/packages/stress) /tmp/xfs-92661e8d/yarn run lint exited (1)
Common_CI
Process completed with exit code 1.
Multinode_Ent
Process completed with exit code 1.

Artifacts

Produced during runtime
Name Size
river-node-Multinode
127 KB
river-node-Multinode_Ent
282 KB
river-node-Multinode_Ent_Legacy
98.6 KB