Skip to content

Create composite action to create constructor-based installers #8

Create composite action to create constructor-based installers

Create composite action to create constructor-based installers #8

Triggered via pull request May 7, 2025 20:17
Status Success
Total duration 35s
Artifacts

test-failure.yaml

on: pull_request
conda-root directory does not exist
13s
conda-root directory does not exist
environment-yaml file does not exist
4s
environment-yaml file does not exist
input-directory does not exist
32s
input-directory does not exist
standalone-location file does not exist
12s
standalone-location file does not exist
No conda or mamba binary
10s
No conda or mamba binary
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
environment-yaml file does not exist
Process completed with exit code 1.
environment-yaml file does not exist
File $(cat /home/runner/work/_temp/path.txt) does not exist.
No conda or mamba binary
Process completed with exit code 1.
No conda or mamba binary
Could not find conda or mamba binary.
standalone-location file does not exist
Process completed with exit code 1.
standalone-location file does not exist
File $(cat /home/runner/work/_temp/path.txt) does not exist.
conda-root directory does not exist
Process completed with exit code 1.
conda-root directory does not exist
Directory $(cat /home/runner/work/_temp/path.txt) does not exist.
input-directory does not exist
Process completed with exit code 1.
input-directory does not exist
Directory $(cat /home/runner/work/_temp/path.txt) does not exist.
conda-root directory does not exist
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'.