Hopefully fixing ci runs #16150
Merged
Hopefully fixing ci runs #16150
Conversation
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
|
LGTM. This was a breaking change between upload/download-artifacts v3 and v4, they discovered (not so surprisingly) that uniqueness helps with faster queries. |
|
CC @szarnyasg this will affect artifact names for the pre-release downloads I think |
|
If change is undesirable, it can be fixed via providing the artifact name (either |
|
Would be also nice to apply this new naming to extensions artifact name like linux-extensions-64-aarch64 |
|
Thanks! |
Antonov548
added a commit
to Antonov548/duckdb-r
that referenced
this pull request
Feb 27, 2025
Parquet Reader: Split `CreateReader` into two separate stages - `ParseSchema` and `CreateReader` (duckdb/duckdb#16161) Removed the last CI job that used the Ubuntu 18 setup (duckdb/duckdb#16155) Hopefully fixing ci runs (duckdb/duckdb#16150) Add uniq_ptr_cast for interpreted benchmark. (duckdb/duckdb#16151)
krlmlr
pushed a commit
to duckdb/duckdb-r
that referenced
this pull request
Mar 5, 2025
Parquet Reader: Split `CreateReader` into two separate stages - `ParseSchema` and `CreateReader` (duckdb/duckdb#16161) Removed the last CI job that used the Ubuntu 18 setup (duckdb/duckdb#16155) Hopefully fixing ci runs (duckdb/duckdb#16150) Add uniq_ptr_cast for interpreted benchmark. (duckdb/duckdb#16151)
krlmlr
added a commit
to duckdb/duckdb-r
that referenced
this pull request
May 15, 2025
Parquet Reader: Split `CreateReader` into two separate stages - `ParseSchema` and `CreateReader` (duckdb/duckdb#16161) Removed the last CI job that used the Ubuntu 18 setup (duckdb/duckdb#16155) Hopefully fixing ci runs (duckdb/duckdb#16150) Add uniq_ptr_cast for interpreted benchmark. (duckdb/duckdb#16151)
krlmlr
added a commit
to duckdb/duckdb-r
that referenced
this pull request
May 15, 2025
Parquet Reader: Split `CreateReader` into two separate stages - `ParseSchema` and `CreateReader` (duckdb/duckdb#16161) Removed the last CI job that used the Ubuntu 18 setup (duckdb/duckdb#16155) Hopefully fixing ci runs (duckdb/duckdb#16150) Add uniq_ptr_cast for interpreted benchmark. (duckdb/duckdb#16151)
krlmlr
added a commit
to duckdb/duckdb-r
that referenced
this pull request
May 17, 2025
Parquet Reader: Split `CreateReader` into two separate stages - `ParseSchema` and `CreateReader` (duckdb/duckdb#16161) Removed the last CI job that used the Ubuntu 18 setup (duckdb/duckdb#16155) Hopefully fixing ci runs (duckdb/duckdb#16150) Add uniq_ptr_cast for interpreted benchmark. (duckdb/duckdb#16151)
krlmlr
added a commit
to duckdb/duckdb-r
that referenced
this pull request
May 18, 2025
Parquet Reader: Split `CreateReader` into two separate stages - `ParseSchema` and `CreateReader` (duckdb/duckdb#16161) Removed the last CI job that used the Ubuntu 18 setup (duckdb/duckdb#16155) Hopefully fixing ci runs (duckdb/duckdb#16150) Add uniq_ptr_cast for interpreted benchmark. (duckdb/duckdb#16151)
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.
I seem to recall that it used to be fine to re-use an artifact name but this seems to be no longer the case :/