Running a PMP ENSO diagnostic end-to-end fails on macOS because the provider's conda environment lives under the default config dir ~/Library/Application Support/climate_ref/software/..., whose path contains a space. Console-script shebangs inside that env (#!/Users/.../Library/Application Support/.../bin/python) can't handle the space and get truncated at it.
Seen with ref test-cases mint --provider pmp --diagnostic enso_tel (and enso_proc): the ENSO driver launches, runs for a while, then dies with
FileNotFoundError: [Errno 2] No such file or directory: '/Users/<user>/Library/Application'
Note: moving only REF_RESULTS_ROOT / REF_SCRATCH_ROOT off the space-containing path is not enough — the failure comes from the software/conda prefix, not the output directories.
Environment: macOS, default REF_CONFIGURATION = ~/Library/Application Support/climate_ref (software env under .../software).
Workaround: set REF_SOFTWARE_ROOT to a space-free path and recreate the provider environment there before running.
Suggested fix: reject or normalise whitespace in the software root (fail fast with a clear message), or default the software root to a space-free location on macOS.
Running a PMP ENSO diagnostic end-to-end fails on macOS because the provider's conda environment lives under the default config dir
~/Library/Application Support/climate_ref/software/..., whose path contains a space. Console-script shebangs inside that env (#!/Users/.../Library/Application Support/.../bin/python) can't handle the space and get truncated at it.Seen with
ref test-cases mint --provider pmp --diagnostic enso_tel(andenso_proc): the ENSO driver launches, runs for a while, then dies withNote: moving only
REF_RESULTS_ROOT/REF_SCRATCH_ROOToff the space-containing path is not enough — the failure comes from the software/conda prefix, not the output directories.Environment: macOS, default
REF_CONFIGURATION = ~/Library/Application Support/climate_ref(software env under.../software).Workaround: set
REF_SOFTWARE_ROOTto a space-free path and recreate the provider environment there before running.Suggested fix: reject or normalise whitespace in the software root (fail fast with a clear message), or default the software root to a space-free location on macOS.