Open
Conversation
Contributor
I do not like this for libraries. CI should run against the latest versions |
Contributor
|
I wonder if we should just port this to GHA like I did for aiodynamo. There I also made it so poetry only locks in one step that is re-used by the rest. |
Author
yeah thats fair |
Author
yeah GHA could work too.. whichever CI tool we use though, think we should separate out browser tests (relatively flaky) vs other tests |
This file contains hidden or 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
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.
Currently build is quite slow (> 8m), and if a test fails we need to re-try the entire job.
This PR aims to make builds faster, by
poetry.lockfor faster package resolution