[good] uploading training script that works? #678
Annotations
1 error and 7 warnings
|
Run conda-incubator/setup-miniconda@v2
The process '/usr/share/miniconda3/condabin/mamba' failed with exit code 1
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, conda-incubator/setup-miniconda@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Run conda-incubator/setup-miniconda@v2
Future Miniforge releases will NOT build Mambaforge installers. We advise you switch to Miniforge at your earliest convenience. More details at https://conda-forge.org/news/2024/07/29/sunsetting-mambaforge/.
|
|
Run conda-incubator/setup-miniconda@v2
Mamba support is still experimental and can result in differently solved environments!
|
|
Run conda-incubator/setup-miniconda@v2
Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='conda.anaconda.org', port=443): Read timed out. (read timeout=60.0)")': /torch/noarch/repodata.json.zst
|
|
Run conda-incubator/setup-miniconda@v2
Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='conda.anaconda.org', port=443): Read timed out. (read timeout=60.0)")': /torch/linux-64/repodata.json.zst
|
|
Run conda-incubator/setup-miniconda@v2
CondaHTTPError: HTTP 502 BAD GATEWAY for url <https://conda.anaconda.org/torch/noarch/repodata.json>
Elapsed: 01:55.812024
CF-RAY: 8c60c0927dabfb44-SJC
A remote server error occurred when trying to retrieve this URL.
A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
fulfill a valid request. The problem may be spurious, and will resolve itself if you
try your request again. If the problem persists, consider notifying the maintainer
of the remote server.
|
Loading