Skip to content

Problem: latest hermes is not used in integration tests #2827

Problem: latest hermes is not used in integration tests

Problem: latest hermes is not used in integration tests #2827

Triggered via pull request July 19, 2024 02:03
@mmsqemmsqe
synchronize #1062
bump_hermes
Status Failure
Total duration 14m 12s
Artifacts

audit.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 1 warning
check
chain.main calls cmd.Execute, which eventually calls blocksync.BlockPool.OnStart
check
chain.main calls cmd.Execute, which eventually calls blocksync.BlockPool.SetPeerRange
check
chain.main calls cmd.Execute, which eventually calls blocksync.NewBlockPool
check
chain.main calls cmd.Execute, which eventually calls blocksync.Reactor.OnStart
check
chain.main calls cmd.Execute, which eventually calls blocksync.Reactor.SwitchToBlockSync
check
app.ValidateMsgTransferDecorator.AnteHandle calls types.ChainAnteDecorators, which eventually calls keeper.Keeper.Timeout
check
app.ValidateMsgTransferDecorator.AnteHandle calls types.ChainAnteDecorators, which eventually calls keeper.Keeper.TimeoutOnClose
check
Process completed with exit code 3.
check
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v3, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/