GH-45305: [CI][Python] Temporarily avoid newer boto3 version #45311
Conversation
This file contains 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
Until Minio gets fixed.
|
@github-actions crossbow submit -g python |
|
|
|
Revision: 6671e83 Submitted crossbow builds: ursacomputing/crossbow @ actions-3dcdd8e768
|
|
@h-vetinari @raulcd I'd like to merge this quickly if it fixes the CI failures |
pitrou
requested review from
assignUser,
jonkeane,
kou and
raulcd
as code owners
raulcd
approved these changes
Jan 20, 2025
github-actions
bot
added
awaiting merge
|
The remaining CI failures (Substrait, Hypothesis, Emscripten) are unrelated. |
|
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit a74eb7e. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 10 possible false positives for unstable benchmarks that are known to sometimes produce them. |
github-merge-queue bot
pushed a commit
to meltano/meltano
that referenced
this pull request
Jan 21, 2025
…atible state backend) (#9035) <!-- Please, go through these steps when you submit a PR. 1. Make sure your branch is not protected. In particular, avoid making PRs from the `main` branch of your fork. 2. Give a descriptive title to your PR. We use semantic titles, and the accepted types and scopes are listed in https://github.com/meltano/meltano/blob/main/.github/semantic.yml. A good title should look like this: ``` feat(cli): The `meltano run` command now accepts a `--timeout` option to limit the time it runs ``` 3. Provide a description of your changes. 4. Put "Closes #XXXX" in your comment to auto-close the issue that your PR fixes (if such). --> ## Description <!-- Describe the changes introduced by this PR --> Example failure: https://github.com/meltano/meltano/actions/runs/12877579377/job/35902245665?pr=9035. We can remove the upper bound once there's a new release of Minio. ## Related Issues * Closes #XXXX * apache/arrow#45305 * minio/minio#20845 * minio/minio#20855 * apache/arrow#45311
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.
Until Minio gets fixed.
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?