From 070b880d69fd9d1416c3af5b842414bdff810a60 Mon Sep 17 00:00:00 2001
From: Bradley Dice <bdice@bradleydice.com>
Date: Thu, 3 Oct 2024 14:15:13 -0500
Subject: [PATCH] Quiet conda warnings. (#729)

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: https://github.com/rapidsai/integration/pull/729
---
 ci/test_conda_nightly_env.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/ci/test_conda_nightly_env.sh b/ci/test_conda_nightly_env.sh
index 1cbd9e83..ee5a0c63 100755
--- a/ci/test_conda_nightly_env.sh
+++ b/ci/test_conda_nightly_env.sh
@@ -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}"