Add "composer.lock" for integration tests #32814
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As "composer.lock" was not versioned the dependencies had to be resolved everytime that the integration tests run, which took some precious time (and power ;-) ). Besides that this also ensures that the versions are consistent/reproducible between different runs. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
CarlSchwan
approved these changes
Jun 10, 2022
juliushaertl
approved these changes
Jun 10, 2022
|
Mmm, integration test federation_features/federated.feature:65 works locally, I do not know what is going on 🤔 |
|
I run So... I do not know why it failed before, but it is probably not related to the specific dependency versions introduced in this pull request. It would be good to keep an eye on that test, though. |
Merged
|
Overriden by #33714 🤷 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As "composer.lock" was not versioned the dependencies had to be resolved everytime that the integration tests run, which took some precious time (and power ;-) ).
Besides that this also ensures that the versions are consistent/reproducible between different runs.