[4.0][INFRA] Update integration tests to clear all possible ivy caches + minor update to S3LogStoreUtilIntegrationTest #4767
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
…inor update to S3LogStoreUtilIntegrationTest (delta-io#3258) <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, please read our contributor guidelines: https://github.com/delta-io/delta/blob/master/CONTRIBUTING.md 2. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP] Your PR title ...'. 3. Be sure to keep the PR description updated to reflect all changes. 4. Please write your PR title to summarize what this PR proposes. 5. If possible, provide a concise example to reproduce the issue for a faster review. 6. If applicable, include the corresponding issue number in the PR title and link it in the body. --> #### Which Delta project/connector is this regarding? <!-- Please add the component selected below to the beginning of the pull request title For example: [Spark] Title of my pull request --> - [ ] Spark - [ ] Standalone - [ ] Flink - [ ] Kernel - [X] Other (INFRA) ## Description During integration testing and QA for the 4.0 preview release we noticed clearing the `~/.ivy2/` caches was not sufficient. This PR updates any scripts that clear artifacts to check for any subfolders that start with ".ivy" and clear any artifacts from there. Also removes the conf setting `ProfileCredentialsProvider` as the credential provider for `S3LogStoreUtilIntegrationTest`. The default credential chain provider should include `ProfileCredentialsProvider` anyways, and removing it allows us to provide credentials in any of the other ways supported in the chain provider. ## How was this patch tested? Ran the `S3LogStoreUtilIntegrationTest` as well as ran `run-integration-tests.py` locally to check it clears the right caches. ## Does this PR introduce _any_ user-facing changes? No. TODO: cherrypick to `branch-4.0`
vkorukanti
approved these changes
Jun 13, 2025
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.
Cherry-pick #3258 to the 4.0 branch