ethereum-optimism / ethereum-optimism/optimism
[op-acceptance-tests] TestERC20Bridge fails on Eris
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 145
Description
This test fails on Eris with logs:
```
t=2025-09-09T06:45:11.299+0000 lvl=info msg="initializing orchestrator" backend=sysext
=== RUN TestERC20Bridge
system.go:28: INFO [09-09|06:45:11.299] Interop is inactive, skipping clusters
system.go:51: INFO [09-09|06:45:11.299] Interop is inactive, skipping supervisors
l2.go:391: INFO [09-09|06:45:11.302] Loaded devnet keys: 42 L1 system keys, 0 L2 user keys
l2.go:391: INFO [09-09|06:45:11.306] Loaded devnet keys: 42 L1 system keys, 0 L2 user keys
eoa.go:176: INFO [09-09|06:45:33.942] deployed WETH chainID=11155111 address=0xA04C1B7e122AcAFbB7DAeB36Cd26816950556F62
erc20_bridge_test.go:30: INFO [09-09|06:45:33.942] Deployed WETH token on L1 address=0xA04C1B7e122AcAFbB7DAeB36Cd26816950556F62
erc20_bridge_test.go:39: INFO [09-09|06:45:33.942] Minting WETH tokens on L1 amount="10,000,000 gwei"
assertions.go:369: ERROR[09-09|06:45:49.613] "\n\tError Trace:\t/data/optimism/op-devstack/dsl/eoa.go:273\n\t \t\t\t\t/data/optimism/op-acceptance-tests/tests/isthmus/erc20_bridge/erc20_bridge_test.go:43\n\tError: \tNot e
qual: \n\t \texpected: 10000000000000000\n\t \tactual : 0\n\t \t\n\t \tDiff:\n\t \t--- Expected\n\t \t+++ Actual\n\t \t@@ -1,3 +1,3 @@\n\t \t (eth.ETH) (len=4) {\n\
t \t- (uint64) 10000000000000000,\n\t \t+ (uint64) 0,\n\t \t (uint64) 0,\n\tTest: \tTestERC20Bridge\n\tMessages: \tmust have expected token balance\n"
--- FAIL: TestERC20Bridge (38.31s)
FAIL
Exiting, code: 1
FAIL github.com/ethereum-optimism/optimism/op-acceptance-tests/tests/isthmus/erc20_bridge 41.551s
```
Contributor guide
Research direction
Start with tests/isthmus/erc20_bridge/erc20_bridge_test.go, especially the balance assertion around line 43, and inspect the failure path at dsl/eoa.go:273. Run TestERC20Bridge on Eris and trace why the expected token balance remains zero; done means the test passes with the intended balance observed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100