Skip to content

Build Wheels & Release #56

Build Wheels & Release

Build Wheels & Release #56

Manually triggered February 7, 2025 23:58
Status Cancelled
Total duration 39m 10s
Artifacts 2

build-wheels-release.yml

on: workflow_dispatch
Matrix: build_wheels
Fit to window
Zoom out
Zoom in

Annotations

93 errors, 88 warnings, and 84 notices
ubuntu-20.04 P3.12 C12.1.0 R T2.4.0
The process '/home/runner/miniconda3/condabin/mamba' failed with exit code null
ubuntu-20.04 P3.12 C12.6.0 R T2.6.0
The process '/home/runner/miniconda3/condabin/mamba' failed with exit code 1
ubuntu-20.04 P3.10 C12.1.0 R T2.5.0
The process '/home/runner/miniconda3/condabin/mamba' failed with exit code 1
ubuntu-20.04 P3.11 C11.8.0 R T2.5.0
The process '/home/runner/miniconda3/condabin/mamba' failed with exit code 1
ubuntu-20.04 P3.13 C R6.0 T2.3.1
Process completed with exit code 1.
ubuntu-20.04 P3.13 C R6.1 T2.4.0
Process completed with exit code 1.
ubuntu-20.04 P3.11 C12.6.0 R T2.6.0
Process completed with exit code 1.
ubuntu-20.04 P3.10 C12.6.0 R T2.6.0
Process completed with exit code 1.
ubuntu-20.04 P3.13 C11.8.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.13 C12.6.0 R T2.6.0
Process completed with exit code 1.
ubuntu-20.04 P3.13 C11.8.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.13 C12.1.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.11 C R5.6 T2.2.2
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.10 C12.6.0 R T2.6.0
Process completed with exit code 1.
ubuntu-20.04 P3.10 C R5.6 T2.2.2
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.11 C12.6.0 R T2.6.0
Process completed with exit code 1.
ubuntu-20.04 P3.10 C R6.0 T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.10 C R6.1 T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.11 C R6.1 T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.12 C R6.0 T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.11 C R6.0 T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.12 C R6.1 T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.13 C11.8.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.12 C11.8.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.13 C12.1.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.11 C12.4.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.12 C11.8.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.12 C12.1.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.13 C12.1.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.11 C12.1.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.10 C12.1.0 R T2.2.2
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.10 C11.8.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.13 C11.8.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.11 C11.8.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.12 C11.8.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.11 C11.8.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.12 C11.8.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.12 C12.1.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.12 C12.6.0 R T2.6.0
Process completed with exit code 1.
ubuntu-20.04 P3.12 C12.4.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.13 C11.8.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.10 C12.1.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.11 C11.8.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.13 C12.1.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.10 C11.8.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.13 C12.1.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.10 C12.4.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.10 C11.8.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.10 C12.1.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.11 C12.1.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.13 C11.8.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.13 C12.4.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.11 C12.1.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.10 C11.8.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-20.04 P3.13 C11.8.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.13 C12.6.0 R T2.6.0
Process completed with exit code 1.
windows-2022 P3.10 C11.8.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.10 C11.8.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.11 C12.1.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.10 C12.1.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.10 C11.8.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.10 C11.8.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.10 C12.1.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.11 C11.8.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.11 C11.8.0 R T2.4.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.11 C12.1.0 R T2.3.1
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.11 C11.8.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.10 C12.4.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.11 C11.8.0 R T2.6.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.10 C12.1.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.11 C12.1.0 R T2.5.0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
windows-2022 P3.11 C12.4.0 R T2.6.0
The run was canceled by @turboderp.
windows-2022 P3.11 C12.4.0 R T2.6.0
The operation was canceled.
windows-2022 P3.12 C12.1.0 R T2.4.0
The run was canceled by @turboderp.
windows-2022 P3.12 C12.1.0 R T2.4.0
The operation was canceled.
windows-2022 P3.12 C12.1.0 R T2.3.1
The run was canceled by @turboderp.
windows-2022 P3.12 C12.1.0 R T2.3.1
The operation was canceled.
windows-2022 P3.12 C11.8.0 R T2.5.0
The run was canceled by @turboderp.
windows-2022 P3.12 C11.8.0 R T2.5.0
The operation was canceled.
windows-2022 P3.12 C12.1.0 R T2.5.0
The run was canceled by @turboderp.
windows-2022 P3.12 C12.1.0 R T2.5.0
The operation was canceled.
windows-2022 P3.12 C11.8.0 R T2.4.0
The run was canceled by @turboderp.
windows-2022 P3.12 C11.8.0 R T2.4.0
The operation was canceled.
windows-2022 P3.12 C12.4.0 R T2.6.0
The run was canceled by @turboderp.
windows-2022 P3.12 C12.4.0 R T2.6.0
The operation was canceled.
windows-2022 P3.12 C11.8.0 R T2.6.0
The run was canceled by @turboderp.
windows-2022 P3.12 C11.8.0 R T2.6.0
The operation was canceled.
windows-2022 P3.13 C12.4.0 R T2.6.0
The run was canceled by @turboderp.
windows-2022 P3.13 C12.4.0 R T2.6.0
The operation was canceled.
windows-2022 P3.12 C11.8.0 R T2.3.1
The run was canceled by @turboderp.
windows-2022 P3.12 C11.8.0 R T2.3.1
The operation was canceled.
windows-2022 P3.13 C11.8.0 R T2.6.0
The run was canceled by @turboderp.
windows-2022 P3.13 C11.8.0 R T2.6.0
The operation was canceled.
ubuntu-20.04 P3.12 C12.1.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.12 C12.1.0 R T2.4.0
error libmamba Could not write to file /home/runner/conda_pkgs_dir/ca-certificates-2025.1.31-hbcca054_0.conda: Bad file descriptor
ubuntu-20.04 P3.12 C12.1.0 R T2.4.0
Download error (23) Failed writing received data to disk/application [https://conda.anaconda.org/conda-forge/linux-64/ca-certificates-2025.1.31-hbcca054_0.conda] Failure writing output to destination, passed 4229 returned 4230
ubuntu-20.04 P3.12 C12.1.0 R T2.4.0
error libmamba Error when extracting package: std::bad_alloc
ubuntu-20.04 P3.12 C12.1.0 R T2.4.0
error libmamba Error when extracting package: std::bad_alloc
ubuntu-20.04 P3.12 C12.1.0 R T2.4.0
corrupted double-linked list
ubuntu-20.04 P3.12 C12.6.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.12 C12.6.0 R T2.6.0
error libmamba Error opening for reading "/home/runner/conda_pkgs_dir/_libgcc_mutex-0.1-conda_forge/info/index.json": No such file or directory
ubuntu-20.04 P3.12 C12.6.0 R T2.6.0
error libmamba Error when extracting package: [json.exception.parse_error.101] parse error at line 1, column 1: attempting to parse an empty input; check that your input string or stream contains the expected JSON
ubuntu-20.04 P3.12 C12.6.0 R T2.6.0
Found incorrect download: _libgcc_mutex. Aborting
ubuntu-20.04 P3.12 C12.6.0 R T2.6.0
# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<< Traceback (most recent call last): File "/home/runner/miniconda3/lib/python3.12/site-packages/conda/exception_handler.py", line 18, in __call__ return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 960, in exception_converter raise e File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 953, in exception_converter exit_code = _wrapped_main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 899, in _wrapped_main result = do_call(parsed_args, p) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 768, in do_call exit_code = create(args, parser) ^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 603, in create return install(args, parser, "create") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 559, in install transaction.fetch_extract_packages() RuntimeError: Found incorrect download: _libgcc_mutex. Aborting `$ /home/runner/miniconda3/condabin/mamba create --name exllama python=3.12` environment variables: CIO_TEST=<not set> CONDA=/home/runner/miniconda3 CONDA_ROOT=/home/runner/miniconda3 CURL_CA_BUNDLE=<not set> DEPLOYMENT_BASEPATH=/opt/runner GITHUB_EVENT_PATH=/home/runner/work/_temp/_github_workflow/event.json GITHUB_PATH=/home/runner/work/_temp/_runner_file_commands/add_path_92af5851-9774- 43ed-b512-3aaeed116add LD_LIBRARY_PATH=/opt/hostedtoolcache/Python/3.12.9/x64/lib LD_PRELOAD=<not set> PATH=/home/runner/miniconda3/condabin:/opt/hostedtoolcache/Python/3.12.9/x6 4/bin:/opt/hostedtoolcache/Python/3.12.9/x64:/snap/bin:/home/runner/.l ocal/bin:/opt/pipx_bin:/home/runner/.cargo/bin:/home/runner/.config/co mposer/vendor/bin:/usr/local/.ghcup/bin:/home/runner/.dotnet/tools:/us r/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/ usr/local/games:/snap/bin REQUESTS_CA_BUNDLE=<not set> SELENIUM_JAR_PATH=/usr/share/java/selenium-server.jar SSL_CERT_FILE=<not set> SWIFT_PATH=/usr/share/swift/usr/bin pythonLocation=/opt/hostedtoolcache/Python/3.12.9/x64 active environment : None user config file : /home/runner/.condarc populated config files : /home/runner/miniconda3/.condarc /home/runner/.condarc conda version : 24.11.3 conda-build version : not installed python version : 3.12.8.final.0 solver : libmamba (default) virtual packages : __archspec=1=zen2 __conda=24.11.3=0 __glibc=2.31=0 __linux=5.15.0=0 __unix=0=0 base environment : /home/runner/miniconda3 (writable) conda av data dir : /home/runner/miniconda3/etc/conda conda av metadata url : None channel URLs : https://conda.anaconda.org/conda-forge/linux-64 https://conda.anaconda.org/conda-forge/noarch package cache : /home/runner/conda_pkgs_dir envs directories : /home/runner/miniconda3/envs /home/runner/.conda/envs platform : linux-64 user-agent : conda/24.11.3 requests/2.32.3 CPython/3.12.8 Linux/5.15.0-1078-azure ubuntu/20.04.6 glibc/2.31 solver/libmamba conda-libmamba-solver/24.9.0 libmambapy/1.5.12
ubuntu-20.04 P3.10 C12.1.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.10 C12.1.0 R T2.5.0
error libmamba Error when extracting package: Could not stat info/test/test_time_dependencies.json
ubuntu-20.04 P3.10 C12.1.0 R T2.5.0
Found incorrect download: ca-certificates. Aborting
ubuntu-20.04 P3.10 C12.1.0 R T2.5.0
# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<< Traceback (most recent call last): File "/home/runner/miniconda3/lib/python3.12/site-packages/conda/exception_handler.py", line 18, in __call__ return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 960, in exception_converter raise e File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 953, in exception_converter exit_code = _wrapped_main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 899, in _wrapped_main result = do_call(parsed_args, p) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 768, in do_call exit_code = create(args, parser) ^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 603, in create return install(args, parser, "create") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 559, in install transaction.fetch_extract_packages() RuntimeError: Found incorrect download: ca-certificates. Aborting `$ /home/runner/miniconda3/condabin/mamba create --name exllama python=3.10` environment variables: CIO_TEST=<not set> CONDA=/home/runner/miniconda3 CONDA_ROOT=/home/runner/miniconda3 CURL_CA_BUNDLE=<not set> DEPLOYMENT_BASEPATH=/opt/runner GITHUB_EVENT_PATH=/home/runner/work/_temp/_github_workflow/event.json GITHUB_PATH=/home/runner/work/_temp/_runner_file_commands/add_path_a8a25d6e-62e2- 4eaa-8a01-d253ed8177bd LD_LIBRARY_PATH=/opt/hostedtoolcache/Python/3.10.16/x64/lib LD_PRELOAD=<not set> PATH=/home/runner/miniconda3/condabin:/opt/hostedtoolcache/Python/3.10.16/x 64/bin:/opt/hostedtoolcache/Python/3.10.16/x64:/snap/bin:/home/runner/ .local/bin:/opt/pipx_bin:/home/runner/.cargo/bin:/home/runner/.config/ composer/vendor/bin:/usr/local/.ghcup/bin:/home/runner/.dotnet/tools:/ usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games :/usr/local/games:/snap/bin REQUESTS_CA_BUNDLE=<not set> SELENIUM_JAR_PATH=/usr/share/java/selenium-server.jar SSL_CERT_FILE=<not set> SWIFT_PATH=/usr/share/swift/usr/bin pythonLocation=/opt/hostedtoolcache/Python/3.10.16/x64 active environment : None user config file : /home/runner/.condarc populated config files : /home/runner/miniconda3/.condarc /home/runner/.condarc conda version : 24.11.3 conda-build version : not installed python version : 3.12.8.final.0 solver : libmamba (default) virtual packages : __archspec=1=zen2 __conda=24.11.3=0 __glibc=2.31=0 __linux=5.15.0=0 __unix=0=0 base environment : /home/runner/miniconda3 (writable) conda av data dir : /home/runner/miniconda3/etc/conda conda av metadata url : None channel URLs : https://conda.anaconda.org/conda-forge/linux-64 https://conda.anaconda.org/conda-forge/noarch package cache : /home/runner/conda_pkgs_dir envs directories : /home/runner/miniconda3/envs /home/runner/.conda/envs platform : linux-64 user-agent : conda/24.11.3 requests/2.32.3 CPython/3.12.8 Linux/5.15.0-1078-azure ubuntu/20.04.6 glibc/2.31 solver/libmamba conda-libmamba-solver/24.9.0 libmambapy/1.5.12
ubuntu-20.04 P3.11 C11.8.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.11 C11.8.0 R T2.5.0
error libmamba Error when extracting package: Could not chdir info/recipe/parent/tests/libhowdy.h
ubuntu-20.04 P3.11 C11.8.0 R T2.5.0
Found incorrect download: _openmp_mutex. Aborting
ubuntu-20.04 P3.11 C11.8.0 R T2.5.0
# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<< Traceback (most recent call last): File "/home/runner/miniconda3/lib/python3.12/site-packages/conda/exception_handler.py", line 18, in __call__ return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 960, in exception_converter raise e File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 953, in exception_converter exit_code = _wrapped_main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 899, in _wrapped_main result = do_call(parsed_args, p) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 768, in do_call exit_code = create(args, parser) ^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 603, in create return install(args, parser, "create") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/miniconda3/lib/python3.12/site-packages/mamba/mamba.py", line 559, in install transaction.fetch_extract_packages() RuntimeError: Found incorrect download: _openmp_mutex. Aborting `$ /home/runner/miniconda3/condabin/mamba create --name exllama python=3.11` environment variables: CIO_TEST=<not set> CONDA=/home/runner/miniconda3 CONDA_ROOT=/home/runner/miniconda3 CURL_CA_BUNDLE=<not set> DEPLOYMENT_BASEPATH=/opt/runner GITHUB_EVENT_PATH=/home/runner/work/_temp/_github_workflow/event.json GITHUB_PATH=/home/runner/work/_temp/_runner_file_commands/add_path_f6474fc6-e0b4- 4ea3-b8ce-ae98c76a5fdc LD_LIBRARY_PATH=/opt/hostedtoolcache/Python/3.11.11/x64/lib LD_PRELOAD=<not set> PATH=/home/runner/miniconda3/condabin:/opt/hostedtoolcache/Python/3.11.11/x 64/bin:/opt/hostedtoolcache/Python/3.11.11/x64:/snap/bin:/home/runner/ .local/bin:/opt/pipx_bin:/home/runner/.cargo/bin:/home/runner/.config/ composer/vendor/bin:/usr/local/.ghcup/bin:/home/runner/.dotnet/tools:/ usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games :/usr/local/games:/snap/bin REQUESTS_CA_BUNDLE=<not set> SELENIUM_JAR_PATH=/usr/share/java/selenium-server.jar SSL_CERT_FILE=<not set> SWIFT_PATH=/usr/share/swift/usr/bin pythonLocation=/opt/hostedtoolcache/Python/3.11.11/x64 active environment : None user config file : /home/runner/.condarc populated config files : /home/runner/miniconda3/.condarc /home/runner/.condarc conda version : 24.11.3 conda-build version : not installed python version : 3.12.8.final.0 solver : libmamba (default) virtual packages : __archspec=1=zen2 __conda=24.11.3=0 __glibc=2.31=0 __linux=5.15.0=0 __unix=0=0 base environment : /home/runner/miniconda3 (writable) conda av data dir : /home/runner/miniconda3/etc/conda conda av metadata url : None channel URLs : https://conda.anaconda.org/conda-forge/linux-64 https://conda.anaconda.org/conda-forge/noarch package cache : /home/runner/conda_pkgs_dir envs directories : /home/runner/miniconda3/envs /home/runner/.conda/envs platform : linux-64 user-agent : conda/24.11.3 requests/2.32.3 CPython/3.12.8 Linux/5.15.0-1078-azure ubuntu/20.04.6 glibc/2.31 solver/libmamba conda-libmamba-solver/24.9.0 libmambapy/1.5.12
ubuntu-20.04 P3.11 C12.6.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.10 C12.6.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.13 C11.8.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.13 C12.1.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.13 C12.6.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.13 C11.8.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.13 C12.1.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.10 C12.6.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.11 C12.6.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.13 C11.8.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.12 C11.8.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.13 C12.1.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.11 C12.4.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.12 C11.8.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.12 C12.1.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.13 C12.1.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.11 C12.1.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.10 C12.1.0 R T2.2.2
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.10 C11.8.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.13 C11.8.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.11 C11.8.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.12 C11.8.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.11 C11.8.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.12 C11.8.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.12 C12.1.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.12 C12.6.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.12 C12.4.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.13 C11.8.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.10 C12.1.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.11 C11.8.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.13 C12.1.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.10 C11.8.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.13 C12.1.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.10 C12.4.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.10 C11.8.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.10 C12.1.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.11 C12.1.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.13 C11.8.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.13 C12.4.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.11 C12.1.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.10 C11.8.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
ubuntu-20.04 P3.13 C11.8.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.13 C12.6.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.10 C11.8.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.10 C11.8.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.11 C12.1.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.10 C12.1.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.10 C11.8.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.10 C11.8.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.10 C12.1.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.11 C11.8.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.11 C11.8.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.11 C12.1.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.11 C11.8.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.10 C12.4.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.11 C11.8.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.10 C12.1.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.11 C12.1.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.11 C12.4.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.12 C12.1.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.12 C12.1.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.12 C11.8.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.12 C12.1.0 R T2.5.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.12 C11.8.0 R T2.4.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.12 C12.4.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.12 C11.8.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.13 C12.4.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.12 C11.8.0 R T2.3.1
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
windows-2022 P3.13 C11.8.0 R T2.6.0
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8
Package Version: build-wheels-release.yml#L200
Detected package version is: 0.2.8

Artifacts

Produced during runtime
Name Size Digest
sdist
2.8 MB
sha256:413dfd1f675d6a3a8cbd2c51958d2f612a651c33cc5ed9f68c07339b6c38f3e8
wheel
1.43 MB
sha256:c7955ab9b10c91db3b8ed41459c625f66ca8ba552c601f0e5c896508224fd5e6