Skip to content

feat: migrate CI to arbitrum-testnode composite action#683

Open
douglance wants to merge 4 commits into
mainfrom
dl/parallel
Open

feat: migrate CI to arbitrum-testnode composite action#683
douglance wants to merge 4 commits into
mainfrom
dl/parallel

Conversation

@douglance

Copy link
Copy Markdown
Contributor

Summary

  • Replace OffchainLabs/actions/run-nitro-test-node@feat-simplify with OffchainLabs/arbitrum-testnode@v0.2.0 (snapshot-based, ~10s boot vs ~12min)
  • Rewrite getInformationFromTestnode() to read config from filesystem (ARBITRUM_TESTNODE_CONFIG_DIR) with docker exec fallback for local dev
  • Handle file renames (l2-nodeConfig.json, l3-nodeConfig.json) and batch poster private-key → address derivation
  • Workflow matrix preserved at 4 cells: {v2.1, v3.2} × {6, 18} using structured action inputs

Depends on

Test plan

  • pnpm build passes
  • pnpm lint passes
  • pnpm test:unit — 38 files, 193 tests pass
  • pnpm test:type — 2 files, 9 tests pass
  • Integration tests pass with published testnode images

Replace the live run-nitro-test-node build with the prebuilt
OffchainLabs/arbitrum-testnode@v0.2.7 composite action across the v3.2 and
v2.1 custom-gas-token integration matrix (6 & 18 decimals), and refresh the
audit allowlist.
…ridge reads

- createRollup: thread RollupCreator v2.1 vs v3.2 differences through fee,
  call-value, custom-fee-token allowance/approval, and transaction-request
  building.
- createTokenBridge: let getTokenBridgeContracts / createTokenBridge accept a
  tokenBridgeCreatorAddressOverride so the inbox->deployment mapping is read
  from the creator that performed the deployment, not the chain default.
Read deployment metadata (rollup-creator, L3 chain-owner upgrade executor)
from the testnode config, fund deployer accounts with the custom fee token
(scaled to the token's decimals), route owner actions through the L3-side
upgrade executor, and query the freshly-deployed token bridge creator.
The testnode emits the RollupCreator address in l3deployment.json
(rollup-creator) for every variant CI uses, so read it directly instead of
scanning RollupCreated logs via eth_getLogs. discoverRollupCreatorAddress
only ran when the value was zero, which never happens for the custom-fee
variants, so this is a behavior-preserving cleanup.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant