GH-49609: [CI][R] AMD64 Windows R release fails with IOError: Bucket 'ursa-labs-r-test' not found#49610
Conversation
|
|
…atasets The ursa-labs-r-test S3 bucket no longer exists, causing CI failures. Replace references with the arrow-datasets bucket which is publicly accessible. Update the RestrictedBucket test in C++ to use usgs-landsat, which requires authentication but still returns the region in error headers (testing a different code path than PublicBucket). Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
150b05c to
8256192
Compare
|
CI failure is due to #49586 - this PR fixes previously failing jobs |
raulcd
left a comment
There was a problem hiding this comment.
Looks good to me. Thanks @thisisnic
|
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 0b20b75. There was 1 benchmark result with an error:
There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them. |
|
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 0b20b75. There was 1 benchmark result with an error:
There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…ucket 'ursa-labs-r-test' not found (apache#49610) ### Rationale for this change Bucket closed, need to use new one ### What changes are included in this PR? Update bucket ### Are these changes tested? Will trigger CI ### Are there any user-facing changes? Nope * GitHub Issue: apache#49609 Authored-by: Nic Crane <thisisnic@gmail.com> Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
Rationale for this change
Bucket closed, need to use new one
What changes are included in this PR?
Update bucket
Are these changes tested?
Will trigger CI
Are there any user-facing changes?
Nope