Skip to content

Commit

Permalink
Quiet conda warnings. (#729)
Browse files Browse the repository at this point in the history
This fixes failures in the new testing workflow from #690.

**Update:** the root cause was that `rapids-conda-retry` is sending `2>&1`. The warning is being sent to stderr as intended. The old contents are partially incorrect. We can still solve this by providing `--quiet`, without needing to change `rapids-conda-retry`.

<details><summary>Old issue contents</summary>

Output like this is shown, even with the `--json` flag to conda:
```
==> WARNING: A newer version of conda exists. <==
    current version: 24.9.0
    latest version: 24.9.1

Please update conda by running

    $ conda update -n base -c conda-forge conda
```

The only way to make the output "proper JSON" is to pass `--quiet` as well.


This seems like unintentional behavior from conda. The docs from `conda create --help` literally say:
```
--json                Report all output as json. Suitable for using conda programmatically.
```

</details>

Authors:
  - Bradley Dice (https://github.com/bdice)

Approvers:
  - James Lamb (https://github.com/jameslamb)
  - Mike Sarahan (https://github.com/msarahan)

URL: #729
  • Loading branch information
bdice authored Oct 3, 2024
1 parent fb695dd commit 070b880
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions ci/test_conda_nightly_env.sh
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ rapids-conda-retry \
cuda-version=${CUDA_VERSION} \
--dry-run \
--json \
--quiet \
| tee "${JSON_FILENAME}"

rapids-logger "Parsing results from conda dry-run with rapids=${RAPIDS_VERSION}, python=${RAPIDS_PY_VERSION}, cuda-version=${CUDA_VERSION}"
Expand Down

0 comments on commit 070b880

Please sign in to comment.