conda mambabuild exits 0 when upload fails

[dagardner-nv]

I had an incident where a CI build passed, but failed to upload the build to anaconda. To simulate an upload failure I used an invalid token (--token XYZ) and confirmed that conda mambabuild exited with a status code of 0:

conda mambabuild --token XYZ --label dev --use-local --build-id-pat '{n}-{v}' -c conda-forge -c rapidsai -c rapidsai-nightly -c nvidia ci/conda/recipes/libmrc
Updating build index: /tmp/conda-bld-output

Yields:

Uploading libmrc-22.06.00b-cuda_12.5_h1b95675_393.tar.bz2 to anaconda.org
Using Anaconda API: https://api.anaconda.org
[ERROR] ('Authorization token is no longer valid', 401)
Uploading mrc-22.06.00b-cuda_12.5_py310_h5ae46af_393.tar.bz2 to anaconda.org
Using Anaconda API: https://api.anaconda.org
[ERROR] ('Authorization token is no longer valid', 401)
anaconda_upload is not set.  Not uploading wheels: []

INFO :: The inputs making up the hashes for the built packages are as follows:
{
  "libmrc-22.06.00b-cuda_12.5_h1b95675_393.tar.bz2": {
    "recipe": {
      "__glibc": "__glibc >=2.28,<3.0.a0",
      "c_compiler": "gcc",
      "c_compiler_version": "12.1",
      "cuda_compiler": "cuda-nvcc",
      "cuda_compiler_version": "12.5",
      "cxx_compiler": "gxx",
      "cxx_compiler_version": "12.1",
      "rapids_version": "24.10",
      "target_platform": "linux-64"
    }
  },
  "mrc-22.06.00b-cuda_12.5_py310_h5ae46af_393.tar.bz2": {
    "recipe": {
      "numpy": "1.22",
      "rapids_version": "24.10",
      "target_platform": "linux-64"
    }
  }
}


####################################################################################
Resource usage summary:

Total time: 0:09:28.4
CPU usage: sys=0:02:53.4, user=0:29:17.6
Maximum memory usage observed: 32.2G
Total disk usage observed (not including envs): 720.5K
# echo $?
0