Skip to content

Conversation

samansmink
Copy link
Contributor

This pr contains a few changes to the CI that should bring a decent reduction in overal CI runner load.

  1. For Node and Python, we only run the latest and oldest versions if the branch != master
  2. When a PR only touches files for node/python/R or their respective yml files, we only run the CI thats actually relevant.
  3. OSX CI is never run for PRs, only after merging on the push event of master. Reasoning behind this is that if a test passes linux CI it will almost certainly also pass OSX ci and the OSX runners tend to be a bottleneck.

Potential further improvements
I could move tools/odbc and tools/jdbc into separate yml files and add similar optimization to only run the relevant ci for those directories. I could also add this to this PR?

For more drastic changes in CI runner load we could consider running the CI only on a specific subset pull_request events. For example we could only run the CI on the pull_request.opened and and pull_request.review_requested events (see github docs), which would mean that CI will run automatically on the initial pr open, but for the ci to be rerun when the author has made changes, the author has to explicitly request a review, which will then trigger the CI. However, whether this is a development workflow we want is up for discussion. I'd say it makes sense to wait out this pr and see if CI queue/run times improve enough to leave it as is.

@Mytherin
Copy link
Collaborator

Thanks! Looks excellent. It seems the NodeJS and Python OSX builds are still running in the PR, can we disable those as well for PRs?

@Mytherin Mytherin merged commit d13fbab into duckdb:master Mar 18, 2022
Mytherin pushed a commit that referenced this pull request Oct 13, 2024
Integer division in C++ rounds towards 0, not down.
This was impacting all resolutions hour and below.

fixes: duckdblabs/duckdb-internal#3251
Mytherin added a commit that referenced this pull request Oct 13, 2024
Integer division in C++ rounds towards 0, not down. This was impacting
all resolutions hour and below.

fixes: duckdblabs/duckdb-internal#3251
github-actions bot pushed a commit to duckdb/duckdb-r that referenced this pull request Oct 17, 2024
github-actions bot added a commit to duckdb/duckdb-r that referenced this pull request Oct 17, 2024
Internal duckdb/duckdb#3251: DateDiff Across Epoch (duckdb/duckdb#14338)

Co-authored-by: krlmlr <krlmlr@users.noreply.github.com>
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.

2 participants