Skip to content

Update DEX WASM tests to work with the update version of the WASM SDK. #5832

Update DEX WASM tests to work with the update version of the WASM SDK.

Update DEX WASM tests to work with the update version of the WASM SDK. #5832

Triggered via pull request November 22, 2024 12:36
Status Failure
Total duration 38m 20s
Artifacts

ci.yml

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

Annotations

7 errors
ci (integration tests coreum-stress)
The self-hosted runner: self-hosted-runne-4 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
ci (integration tests coreum-ibc)
The self-hosted runner: self-hosted-runner-9 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
ci (integration tests coreum-upgrade-v4.0.0)
The self-hosted runner: self-hosted-runne-5 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
ci (integration tests coreum-modules)
Process completed with exit code 2.
ci (test)
Process completed with exit code 2.
ci (lint)
The self-hosted runner: self-hosted-runner-9 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
ci (test-fuzz)
The self-hosted runner: self-hosted-runne-5 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.