For developer builds we use a pinned version of the e2e subs artifact. The intent is we avoid flaky tests when new features are added to go-algorand which are not yet supported by Indexer. Currently the version of go-algorand is not pinned. In some cases this can cause problems. Especially for development builds where compatibility guarantees are weaker.
Solution
you should be able to specify the algod release with an environment variable, and it should be set in the CircleCi config.
Problem
For developer builds we use a pinned version of the e2e subs artifact. The intent is we avoid flaky tests when new features are added to go-algorand which are not yet supported by Indexer. Currently the version of go-algorand is not pinned. In some cases this can cause problems. Especially for development builds where compatibility guarantees are weaker.
Solution
you should be able to specify the algod release with an environment variable, and it should be set in the CircleCi config.