Open 0xTimepunk opened 1 year ago
This might be related to the recently added cache - have you tried manually deleting the cache by following the instructions in the README?
I went to the mentioned caches page and couldn't find any cache.
I added a cache: false
to the CI file. Also the issue seems random, because when you try sometimes re-running the CI job it passes without errors.
This is likely because the RPC you are talking to either times out, or does not have the data available. Remember that non-archive nodes only support accessing state for the n latest blocks.
This is likely because the RPC you are talking to either times out, or does not have the data available. Remember that non-archive nodes only support accessing state for the n latest blocks.
We are using quicknodes for all the chains we need the service and all of our nodes are archive nodes. So unless they are timing out, which I would find odd, I would rule out that.
Is it possible that what timeouts is because of foundry itself, expecting to get return data faster than what is possible?. Doesn't seem related foundry-toolchain actually.
Hi,
During our test suite with foundry-toolchain/github actions the following error appears:
which appears to be related to https://github.com/foundry-rs/foundry/issues/3874 but was fixed apparently in a nightly build at the end of December as commented here: https://github.com/foundry-rs/foundry/issues/3874#issuecomment-1358862493
It seems to us that the toolchain is possibly not using the latest version with this fix?
Our CI is supposedly using foundry "nightly" build:
Thank you