Skip to content

ci: update testnode action ref after repo rename to arbitrum-litro - #647

Open
douglance wants to merge 3 commits into
mainfrom
dl/fix-testnode-action-rename
Open

ci: update testnode action ref after repo rename to arbitrum-litro#647
douglance wants to merge 3 commits into
mainfrom
dl/fix-testnode-action-rename

Conversation

@douglance

Copy link
Copy Markdown
Contributor

Summary

One-line workflow fix: OffchainLabs/arbitrum-testnode was renamed to OffchainLabs/arbitrum-litro on 2026-07-22 (~16:00 UTC). GitHub Actions does not follow repo renames when resolving uses: references, so the testnode job now fails at Set up job with Unable to resolve action. Repository not found: OffchainLabs/arbitrum-testnode.

Verified the pinned v0.2.4 tag exists on arbitrum-litro. The image-repository: ghcr.io/offchainlabs/arbitrum-testnode-ci input is untouched — GHCR package names are not affected by the repo rename.

Same fix as OffchainLabs/arbitrum-indexer#99, where E2E is confirmed green after the change.

OffchainLabs/arbitrum-testnode was renamed to OffchainLabs/arbitrum-litro.
GitHub Actions does not follow repo renames when resolving 'uses:'
references, so jobs using this action fail at setup with "Unable to
resolve action. Repository not found". The pinned tag exists on the
renamed repo; only the action reference needs updating.
@cla-bot cla-bot Bot added the cla-signed label Jul 22, 2026
Bump to the latest arbitrum-litro release, confirmed compatible by the
litro team. Matching GHCR image variants exist for v0.2.9.
@douglance

Copy link
Copy Markdown
Contributor Author

Also bumped to v0.2.9 per litro-team compatibility confirmation: action ref and version input (was action v0.2.4 / image v0.2.2). Inputs used here (l3-enabled, fee-token-decimals, network-config-path) are unchanged between v0.2.4 and v0.2.9; v0.2.9 GHCR image variants verified present.

The v0.2.9-v0.2.11 testnode images are missing the anvil state (fixed in
litro PR #30 / v0.2.12 images), and the v0.2.12 snapshot regenerated chain
state, so deployed test-token addresses and funded accounts no longer
match the constants these tests use. Pin the previously green versions;
bumping to a current release needs a coordinated snapshot migration.
@douglance

Copy link
Copy Markdown
Contributor Author

Reverted the v0.2.9/v0.2.12 bump back to the last known-good pin (proven green earlier today). Two findings from the attempt:

  1. v0.2.9–v0.2.11 images are broken — missing anvil state, container exits before the L1 RPC comes up (fixed by litro PR feat: add getL2ToL1Events static method to L2ToL1Message #30; first good images are v0.2.12).
  2. v0.2.12 regenerated the snapshot chain state — deployed test-token addresses and funded accounts no longer match the constants consumer tests hardcode (e.g. txgen reverts / missing ERC20 at the pinned address). Moving to current images is a coordinated snapshot migration per consumer, not a CI pin — out of scope for the rename fix.

This PR is back to exactly the rename fix, which is all it needs to be.

@douglance

Copy link
Copy Markdown
Contributor Author

The failing Audit check is fixed separately in #648 (new advisory wave from ~2026-07-20; resolutions bumps). Once #648 merges, re-run or rebase this PR for a fully green board.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant