Skip to content

introduce IntentGateway #1980

introduce IntentGateway

introduce IntentGateway #1980

Triggered via pull request February 13, 2025 14:45
@seunlanlegeseunlanlege
opened #385
Status Failure
Total duration 37m 40s
Artifacts

ci.yml

on: pull_request_target
Check Workspace
1m 35s
Check Workspace
Unit Tests
1m 12s
Unit Tests
Integration Tests
29s
Integration Tests
Check ismp-solidity
1m 0s
Check ismp-solidity
Hyperclient Integration Tests
6m 6s
Hyperclient Integration Tests
Matrix: Check Wasm Crates
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 7 warnings
Integration Tests
Some specified paths were not resolved, unable to cache dependencies.
Integration Tests
Process completed with exit code 14.
Unit Tests
Some specified paths were not resolved, unable to cache dependencies.
Check Workspace
Some specified paths were not resolved, unable to cache dependencies.
Integration Tests
No existing directories found containing cache-dependency-path="evm/yarn.lock"
Check ismp-solidity
Cache not found for keys: linux-foundry-chain-fork-check-solidity-fdb487eef21ca3fadbbc7cb86dadd3b83235ed2f, linux-foundry-chain-fork-check-solidity-, linux-foundry-chain-fork-
Unit Tests
No existing directories found containing cache-dependency-path="evm/yarn.lock"
Check Workspace
No existing directories found containing cache-dependency-path="evm/yarn.lock"
Check Wasm Crates (nexus-runtime)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Check Wasm Crates (nexus-runtime)
Cache not found for keys: v0-rust-check-wasm-Linux-af629c20-3ca299f7, v0-rust-check-wasm-Linux-af629c20
Check Wasm Crates (gargantua-runtime)
Cache not found for keys: v0-rust-check-wasm-Linux-af629c20-3ca299f7, v0-rust-check-wasm-Linux-af629c20