Skip to content

fix: use separate chain id for mock l1 #4459

fix: use separate chain id for mock l1

fix: use separate chain id for mock l1 #4459

Triggered via pull request February 11, 2025 03:24
Status Success
Total duration 1h 17m 27s
Artifacts

ci.yml

on: pull_request
Test and Build Go Modules
5m 14s
Test and Build Go Modules
Foundry Checks and Reports
8m 28s
Foundry Checks and Reports
Test and Build Contracts Scripts
5m 16s
Test and Build Contracts Scripts
infrastructure  /  Setup and Test Nomad Cluster
1h 8m
infrastructure / Setup and Test Nomad Cluster
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Test and Build Go Modules
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
Test and Build Go Modules
No github_token supplied, API requests will be subject to stricter rate limiting
Test and Build Contracts Scripts
Found more than One contract per file. 2 contracts found!
Test and Build Contracts Scripts
Cache not found for keys: linux-foundry-chain-fork-contracts-af9c90182b6f1c69d4a446e54c9004c32546b82f, linux-foundry-chain-fork-contracts-, linux-foundry-chain-fork-
Foundry Checks and Reports
Cache not found for keys: linux-foundry-chain-fork-foundry-af9c90182b6f1c69d4a446e54c9004c32546b82f, linux-foundry-chain-fork-foundry-, linux-foundry-chain-fork-
infrastructure / Setup and Test Nomad Cluster
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
infrastructure / Setup and Test Nomad Cluster
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