-
Notifications
You must be signed in to change notification settings - Fork 84
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
Build conda nightlies jobs are failing on main for aarch64 #659
Comments
Taking a look at the logs, a few things look off.
Attempting to finalize metadata for datafusion
conda-forge/linux-64 Using cache
conda-forge/noarch Using cache
Reloading output folder:
/home/runner/work/datafusion-python/datafusion-python/packages
warning libmamba Cache file "/home/runner/conda_pkgs_dir/cache/09cdf8bf.json" was modified by another program
...
Conda detected a mismatch between the expected content and downloaded content
for url 'https://conda.anaconda.org/conda-forge/noarch/rust-std-x86_64-unknown-linux-gnu-1.77.2-h2c6d0dc_0.conda'.
download saved to: /home/runner/conda_pkgs_dir/rust-std-x86_64-unknown-linux-gnu-1.77.2-h2c6d0dc_0.conda
expected sha256: a482597672076f47c83d0dd3f204eb437007b99ada4d630d56fa64b4b193c5db
actual sha256: 73f7537db6bc0471135a85a261798abe77e7e83794f945a0355c4068973f31f6 The things I'd like to try, in order.
|
The builds are failing for `aarch64`, and one log message hints that concurrent builds are messing with the same cache. Ref: apache#659
The `actual` sha256 hashes match both what I calculate by downloading and running `sha256sum` and what is posted on conda-forge. I suspect then that our build is using some bad cached value as the "expected". conda-forge: https://conda.anaconda.org/conda-forge/noarch/ Ref: apache#659
The builds are failing for `aarch64`, and one log message hints that concurrent builds are messing with the same cache. Ref: apache#659
The `actual` sha256 hashes match both what I calculate by downloading and running `sha256sum` and what is posted on conda-forge. I suspect then that our build is using some bad cached value as the "expected". conda-forge: https://conda.anaconda.org/conda-forge/noarch/ Ref: apache#659
Investigating further. The
So, I tried cleaning out the cache, but that only caused the builds to break in a new way... Adding in variants from internal_defaults
Adding in variants from config.variant
Adding in variants from argument_variants
Error: bad character '-' in package/version: publish-docs.1a240507 Closing the PR for now. |
Ah, Apparently, |
The `actual` sha256 hashes match both what I calculate by downloading and running `sha256sum` and what is posted on conda-forge. I suspect then that our build is using some bad cached value as the "expected". conda-forge: https://conda.anaconda.org/conda-forge/noarch/ Ref: apache#659
The `actual` sha256 hashes match both what I calculate by downloading and running `sha256sum` and what is posted on conda-forge. I suspect then that our build is using some bad cached value as the "expected". conda-forge: https://conda.anaconda.org/conda-forge/noarch/ Ref: apache#659
Describe the bug
The aarch 64 jobs for conda nightlies are failing with:
See:
To Reproduce
Expected behavior
Jobs succeed and build for aarch64
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: