test section raises BadZipFile #4842
Labels
source::community
catch-all for issues filed by community members
stale::closed
[bot] closed after being marked as stale
stale
[bot] marked as stale due to inactivity
type::bug
describes erroneous operation, use severity::* to classify the type
Comments
h-vetinari
added
the
type::bug
|
I see https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=685088&view=logs&j=8af117b0-dfa5-5d1c-b02e-a448dd16efdb&t=5255ce7d-8850-5a89-87a7-dc472af37343&l=14598 "Package at D:\bld\win-64\google-cloud-cpp-2.9.0-hf2ff781_0.conda did not contain valid index.json data. Please check the file and remove/redownload if necessary to obtain a valid package." which might be caused by the same issue. Some conda-package-streaming users report tricky garbage collection but conda-build, through conda-package-handling, should be using it correctly. Does this happen every time? Where do we check the exact versions of conda-build etc. being used? |
|
(closed by mistake) |
It happened 2 out of 2 times. I restarted it for a third run just now.
It's all in the logs, but here for your convenience: From section "Install conda-build"host envbuild env |
|
Assuming the newest conda, conda-build and conda-package-streaming, zstd, (python-)zstandard |
|
Any thoughts? Can we add any additional logging to troubleshoot this issue? |
|
Still running into this with conda-forge/google-cloud-cpp-feedstock#130. Is there any version of conda, conda-build, etc. that changed something about this recently, or to which we can downgrade in the meantime? |
3 tasks
|
Not sure if something changed, but conda-forge/google-cloud-cpp-feedstock#132 just passed. :) |
travishathaway
added
the
source::community
|
Should this be moved to https://github.com/conda/conda-package-streaming ? Seems like an issue with not appropriately handling an exception raised by attempting to open a non-zip file 🤷♂️. We could easily transfer this issue over there. |
|
No @travishathaway some part of the code attempted to create a zip file (a .conda file) and then couldn't extract it again. The file might have been empty or not flushed/closed properly before attempting to "open it again". The error is in the creation of the file not the opening of what was probably an empty file. |
|
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
github-actions
bot
added
the
stale::closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
What happened?
In conda-forge/google-cloud-cpp-feedstock#129, we see
The traceback points to code in the conda namespace, but I'm not sure which component is at fault, so raising an issue for the overall conda-build.
Conda Info
Conda Config
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: