Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TestWithIbcEurekaTestSuite can't run with existing README steps #428

Closed
rootulp opened this issue Mar 19, 2025 · 6 comments · Fixed by #432
Closed

TestWithIbcEurekaTestSuite can't run with existing README steps #428

rootulp opened this issue Mar 19, 2025 · 6 comments · Fixed by #432
Labels
documentation Improvements or additions to documentation testing Issues related to testing

Comments

@rootulp
Copy link
Contributor

rootulp commented Mar 19, 2025

Context

I'm having a difficult time getting RecvPacket to work on an EVM chain so I'm trying to run the e2e tests in this repo to learn more about what I may be doing wrong.

Problem

$ go test -v . -run=TestWithIbcEurekaTestSuite/TestICS20TransferNativeCosmosCoinsToEthereumAndBack_Groth16
2025/03/19 15:08:37 proto: duplicate proto type registered: ibc.lightclients.wasm.v1.MsgStoreCode
2025/03/19 15:08:37 proto: duplicate proto type registered: ibc.lightclients.wasm.v1.MsgStoreCodeResponse
2025/03/19 15:08:37 proto: duplicate proto type registered: ibc.lightclients.wasm.v1.MsgRemoveChecksum
2025/03/19 15:08:37 proto: duplicate proto type registered: ibc.lightclients.wasm.v1.MsgRemoveChecksumResponse
2025/03/19 15:08:37 proto: duplicate proto type registered: ibc.lightclients.wasm.v1.MsgMigrateContract
2025/03/19 15:08:37 proto: duplicate proto type registered: ibc.lightclients.wasm.v1.MsgMigrateContractResponse
2025/03/19 15:08:37 proto: duplicate proto type registered: ibc.lightclients.wasm.v1.ClientState
2025/03/19 15:08:37 proto: duplicate proto type registered: ibc.lightclients.wasm.v1.ConsensusState
2025/03/19 15:08:37 proto: duplicate proto type registered: ibc.lightclients.wasm.v1.ClientMessage
=== RUN   TestWithIbcEurekaTestSuite
=== RUN   TestWithIbcEurekaTestSuite/TestICS20TransferNativeCosmosCoinsToEthereumAndBack_Groth16
    suite.go:67: Unknown Ethereum testnet type:
--- FAIL: TestWithIbcEurekaTestSuite (0.00s)
    --- FAIL: TestWithIbcEurekaTestSuite/TestICS20TransferNativeCosmosCoinsToEthereumAndBack_Groth16 (0.00s)
FAIL
FAIL	github.com/srdtrk/solidity-ibc-eureka/e2e/v8	0.697s
FAIL

Proposal

Add steps to the interchaintestv8/README.md to explain how to run these tests. Seems like an env variable may not be set correctly

@rootulp
Copy link
Contributor Author

rootulp commented Mar 19, 2025

Looks like I have to provide

$ ETH_TESTNET_TYPE=pos go test -v . -run=TestWithIbcEurekaTestSuite/TestICS20TransferNativeCosmosCoinsToEthereumAndBack_Groth16

b/c now hitting a different error

@rootulp
Copy link
Contributor Author

rootulp commented Mar 19, 2025

I also had to update kurtosis-cli

brew upgrade kurtosis-cli

and then start kurtosis

kurtosis engine start

now the test is running

@rootulp
Copy link
Contributor Author

rootulp commented Mar 19, 2025

Test failed. Interesting logs

=== RUN   TestWithIbcEurekaTestSuite/TestICS20TransferNativeCosmosCoinsToEthereumAndBack_Groth16/Start_Relayer
Error: missing field `port` at line 20 column 5
=== RUN   TestWithIbcEurekaTestSuite/TestICS20TransferNativeCosmosCoinsToEthereumAndBack_Groth16/Receive_packet_on_Ethereum/Retrieve_relay_tx
    ibc_eureka_test.go:837:
        	Error Trace:	/Users/rootulp/git/rootulp/celestiaorg/celestia-zkevm-ibc-demo/solidity-ibc-eureka/e2e/interchaintestv8/ibc_eureka_test.go:837
        	            				/Users/rootulp/go/pkg/mod/github.com/stretchr/[email protected]/suite/suite.go:115
        	Error:      	Received unexpected error:
        	            	rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:3000: connect: connection refused"
        	Test:       	TestWithIbcEurekaTestSuite/TestICS20TransferNativeCosmosCoinsToEthereumAndBack_Groth16/Receive_packet_on_Ethereum/Retrieve_relay_tx

so it looks like it's failing to start the relayer. The default relayer config path references a file that is not present on my machine so I copied the example file

cd celestia-zkevm-ibc-demo/solidity-ibc-eureka/programs/relayer
cp config.example.json config.json

@gjermundgaraba
Copy link
Contributor

If you run the tests from the justfile, it will pick up environment variables from .env
There is a .env.example you can use as a basis

@srdtrk srdtrk added documentation Improvements or additions to documentation testing Issues related to testing labels Mar 20, 2025
@rootulp
Copy link
Contributor Author

rootulp commented Mar 20, 2025

Thanks. I tried this:

rm .env
cp .env.example .env
just test-e2e-eureka TestICS20TransferNativeCosmosCoinsToEthereumAndBack_Groth16

and observed the same error and same interesting logs. Still seems like relayer can't start:

=== RUN   TestWithIbcEurekaTestSuite/TestICS20TransferNativeCosmosCoinsToEthereumAndBack_Groth16/Start_Relayer
Error: missing field `port` at line 20 column 5

    ibc_eureka_test.go:837:
        	Error Trace:	/Users/rootulp/git/rootulp/celestiaorg/celestia-zkevm-ibc-demo/solidity-ibc-eureka/e2e/interchaintestv8/ibc_eureka_test.go:837
        	            				/Users/rootulp/go/pkg/mod/github.com/stretchr/[email protected]/suite/suite.go:115
        	Error:      	Received unexpected error:
        	            	rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:3000: connect: connection refused"

@rootulp
Copy link
Contributor Author

rootulp commented Mar 20, 2025

Works now. I had to re-run

just install-relayer && just install-operator

rootulp added a commit to rootulp/solidity-ibc-eureka that referenced this issue Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation testing Issues related to testing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants