Replace conda-mambabuild with conda-build - #752
Conversation
These are now equivalent in behavior. However support for `conda-mambabuild` is being dropped. So switch to `conda-build`.
The default behavior of `conda-build` is to use packages from its local cache. Given this, we don't need this flag. It also causes conda-build to look in a different place than we typically use for the package cache on CI, which causes its own problems.
| rapids-conda-retry build \ | ||
| --use-local \ |
There was a problem hiding this comment.
As conda-build always uses its local cache, the --use-local flag is unneeded
Additionally it appears conda-build has a bug that causes it to look inside its package cache before it is created, which causes the following CI error
UnavailableInvalidChannel: HTTP 404 UNAVAILABLE OR INVALID for channel opt/conda/conda-bld <file:///opt/conda/conda-bld>
The channel is not accessible or is invalid.
You will need to adjust your conda configuration to proceed.
Use `conda config --show channels` to view your configuration's current state,
and use `conda config --show-sources` to view config file locations.
As of conda 4.3, a valid channel must contain a `noarch/repodata.json` and
associated `noarch/repodata.json.bz2` file, even if `noarch/repodata.json` is
empty. Use `conda index /opt/conda/conda-bld`, or create `noarch/repodata.json`
and associated `noarch/repodata.json.bz2`.
Typically we don't use /opt/conda/conda-bld, but use our own package cache location. So this isn't even the right place for it to check
Since we don't need this flag here (nor use it elsewhere), it is easy enough to drop, which fixes all of these issues
There was a problem hiding this comment.
Works for me. I looked through the blame to check why it was added originally... looks like you added it, I think to be sure that the build of integration uses the rapids-xgboost just built in the same build:
So I checked CI logs here to be sure this was working as expected and not falling back to a previous rapids-xgboost nightly.
It is:
BUILD START: ['rapids-xgboost-25.04.00a-cuda11_py310_250227_g07bf842_11.conda']
...
BUILD START: ['rapids-25.04.00a-cuda11_py310_250227_g07bf842_11.conda']
...
rapids-xgboost: 25.04.00a-cuda11_py310_250227_g07bf842_11 file:///tmp/conda-bld-output
...
There was a problem hiding this comment.
Good catch!
Maybe there was a past conda-build issue we were working around with the test phase
|
The |
jameslamb
left a comment
jameslamb
left a comment
There was a problem hiding this comment.
Even if that rapids-logger change was made, you'd still run into issues like what you're facing here because that project isn't built every night (https://github.com/rapidsai/rapids-logger/actions/workflows/build.yaml).
It'd be better to just add rapids-logger to this exclusion list:
integration/ci/check_conda_nightly_env.py
Lines 10 to 13 in 3b43bff
|
/merge |
|
Thanks James! 🙏 |
2 participants
These are now equivalent in behavior. However support for
conda-mambabuildis being dropped. So switch toconda-build.xref: rapidsai/build-planning#149