Don't run stack test on Buildkite #2961
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reduce flakiness of CI by not running Stack test step in Buildkite pipeline.
@jonathanknowles reported a flaky Stack test run in this build: https://buildkite.com/input-output-hk/cardano-wallet/builds/17155#77dce73e-664a-4bb6-9e6b-d5a898a47d5d.
One way we can reduce this flakiness is by not running the tests in the Buildkite pipeline.
My argument for doing so it that doing so adds very little to our test coverage:
We already run the tests as part of the Nix + Cabal CI on Hydra.
The Buildkite and Hydra pipelines both use Nix to provision dependencies.
The Stack test and the Nix + Cabal test both run on the
packet-ipxe-*
machines, so we aren't testing on different machines. See:Buildkite environment https://buildkite.com/input-output-hk/cardano-wallet/builds/17160#1ae5b95d-7a7f-47a8-a1c1-5252a3d0c962:
Hydra build https://hydra.iohk.io/build/7899301#tabs-buildsteps:
The differences between the two invocations are:
So what we are testing by invoking the tests twice is:
For 1, I believe that this isn't something we care to test. This will only find bugs in Stack. For 2, We aren't removing the Stack build step, just the Stack test step, we are still testing that the Stack build works in the given Nix environment.
I do foresee some risks: