[limdor]

Using different versions of the toolchain builders adds unnecessary risk.
We are not aware of any good reasons why someone would like to use different versions of the builder or using different commit hashes in the same build tree.

[limdor]

@dcalavrezo-qorix you created the PR updating coverage without updating the other. Do you see a good reason why someone would want to use a different version of ferrocene toolchain builder for coverage than for the rest?

[dcalavrezo-qorix]

@dcalavrezo-qorix you created the PR updating coverage without updating the other. Do you see a good reason why someone would want to use a different version of ferrocene toolchain builder for coverage than for the rest?

this wasn't intentional. it's harmful since all versions are based on the same ferrocene commit SHA.

so there's no good reason.

Btw, I think we should switch to 1.3.1

FERROCENE_TOOLCHAIN_BUILDER_VERSION = "1.3.1"
...
coverage_tools_sha256 = "9cf5d76b2e505bf2a8b2b47c60f191ac1273f87851ed387e53080b8e5d14dedf",
...
sha256 = "6fd7c7053a80463b2bfd24202de02e16959b18ed185c55b738148e9caac42eff",

[limdor]

@dcalavrezo-qorix you created the PR updating coverage without updating the other. Do you see a good reason why someone would want to use a different version of ferrocene toolchain builder for coverage than for the rest?

this wasn't intentional. it's harmful since all versions are based on the same ferrocene commit SHA.

so there's no good reason.

Btw, I think we should switch to 1.3.1

FERROCENE_TOOLCHAIN_BUILDER_VERSION = "1.3.1"
...
coverage_tools_sha256 = "9cf5d76b2e505bf2a8b2b47c60f191ac1273f87851ed387e53080b8e5d14dedf",
...
sha256 = "6fd7c7053a80463b2bfd24202de02e16959b18ed185c55b738148e9caac42eff",

Thanks for the feedback. About updating to 1.3.1, I did not do because I did not want to do too many changes at once, but I can do it in a follow up.