failed to start chainlink container in integration test

Question

failed to start chainlink container in integration test

yutongp opened this issue 4 years ago · comments

i have ran ./integration/setup without issue.
But when i ran ./integration/run_test, the integration_chainlink container kept restarting.
Here is the log from that container:

2020-09-15T00:10:35Z [INFO]  API exposed for user notreal@fakeemail.ch          cmd/local_client.go:95
2020-09-15T00:10:35Z [DEBUG] eth.Client#Dial(...)                               eth/client.go:110
error starting app: dial tcp 127.0.0.1:8546: connect: connection refused

i didn't change the integration/chainlink.env file under integration which has ETH_DISABLED=true

Kristijan Rebernisak · Answer 1 · Tue Sep 15 2020 16:23:42 GMT+0800 (China Standard Time)

Thanks, @yutongp!

You are correct, this got broken in Chainlink node 0.8.13 release.

We are working on a fix, but until then you can fix the version to 0.8.12 in the Dockerfile to avoid the issue and make the integration tests run.

Yutong Pei · Answer 2 · Wed Sep 16 2020 01:25:26 GMT+0800 (China Standard Time)

@krebernisak Thank you! Will switch to 0.8.12 for now

Kristijan Rebernisak · Answer 3 · Sat Sep 19 2020 00:06:15 GMT+0800 (China Standard Time)

@yutongp should be fixed by smartcontractkit/chainlink#3382, which should be included in a 0.8.16 release later today.

At that point, we can switch back to smartcontract/chainlink:latest.

Kristijan Rebernisak · Answer 4 · Tue Sep 22 2020 17:07:07 GMT+0800 (China Standard Time)

Closing this issue as 0.8.16 is now released, and I confirmed that the bug is fixed.