-
Notifications
You must be signed in to change notification settings - Fork 378
CI: Disable caching #2268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Disable caching #2268
Conversation
weird that the test fails with
but in the CI's
|
Yes, it looks like it isn't being added to the path for some reason. I'm not sure where this comes from, but I suspect some dependency that's not correctly pinned. I noticed that we have some build dependencies without a specific version: Lines 289 to 291 in 904c0b7
But non of them had a release recently, so it could also be a downstream dependency somewhere that doesn't isn't correctly pinned. Or it could be a red-herring, the integration tests are working fine. It seems to be an issue when it is imported from the |
i think we're using the same prompt haha
from kevinjqliu#18 this test passed... maybe it was intermittent or just a bad host machine? |
@kevinjqliu Hahaha nice!
I hope so 🤞 This is pretty annoying :D |
ok this is interesting. the this PR, the test failed. and poetry is using 3.9
my pr, the test passed. and poetry is using 3.10
In fact, if you check all 4 🤔 |
Maybe we should disable the caching for now? It looks like the difference in time is minimal. With caching 3m39s: https://github.com/apache/iceberg-python/actions/runs/16532954029/job/46762141235 |
nice catch, another workaround can be to manually force build-module.py by adding this step in the CI definition
|
@kevinjqliu I'd rather get rid of the native code in this repository, instead of adding workarounds :) Thanks for looking into this 👍 |
<!-- Thanks for opening a pull request! --> <!-- In the case this PR will resolve an issue, please replace ${GITHUB_ISSUE_ID} below with the actual Github issue id. --> <!-- Closes #${GITHUB_ISSUE_ID} --> # Rationale for this change Looks like something changed, which caused the CI to fail: https://github.com/apache/iceberg-python/commits/main/ First attempt to isolate the issue (checking if it is related to coverage) # Are these changes tested? # Are there any user-facing changes? <!-- In the case of user-facing changes, please add the changelog label. -->
Rationale for this change
Looks like something changed, which caused the CI to fail: https://github.com/apache/iceberg-python/commits/main/
First attempt to isolate the issue (checking if it is related to coverage)
Are these changes tested?
Are there any user-facing changes?