Skip to content

Conversation

@y26805
Copy link

@y26805 y26805 commented Oct 12, 2022

Currently build is quite slow (> 8m), and if a test fails we need to re-try the entire job.

image

This PR aims to make builds faster, by

  • checking in poetry.lock for faster package resolution
  • caching
  • parallelizing tests
  • separating build/test steps in the workflow (to make retries easier and faster)
    image

@ojii
Copy link
Contributor

ojii commented Oct 12, 2022

  • checking in poetry.lock for faster package resolution

I do not like this for libraries. CI should run against the latest versions

@ojii
Copy link
Contributor

ojii commented Oct 12, 2022

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.

@y26805
Copy link
Author

y26805 commented Oct 12, 2022

  • checking in poetry.lock for faster package resolution

I do not like this for libraries. CI should run against the latest versions

yeah thats fair

@y26805
Copy link
Author

y26805 commented Oct 12, 2022

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.

yeah GHA could work too.. whichever CI tool we use though, think we should separate out browser tests (relatively flaky) vs other tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants