conda constructor never exits when "No space left on device"

[njzjz]

Checklist

• I added a descriptive title
• I searched open reports and couldn't find a duplicate

What happened?

I am using conda constructor with the GitHub Actions. It threw "No space left on device" error, but the GitHub Actions never stopped.

Traceback (most recent call last):
  File "/usr/share/miniconda/envs/__setup_conda/bin/constructor", line 11, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/share/miniconda/envs/__setup_conda/lib/python3.11/site-packages/constructor/main.py", line 405, in main
    main_build(dir_path, output_dir=out_dir, platform=args.platform,
  File "/usr/share/miniconda/envs/__setup_conda/lib/python3.11/site-packages/constructor/main.py", line 229, in main_build
    create(info, verbose=verbose)
  File "/usr/share/miniconda/envs/__setup_conda/lib/python3.11/site-packages/constructor/shar.py", line 191, in create
    fo.write(chunk)
OSError: [Errno 28] No space left on device

In another build, it didn't give such an error message but just hanged.

I tried to run rm -rf /opt/hostedtoolcache in the beginning to clean the space, per https://github.com/orgs/community/discussions/25678#discussioncomment-5242449. It works.

So, I think the problem is that conda-constructor cannot properly exit when the "no space left on device" error happens.

Conda Info

No response

Conda Config

No response

Conda list

No response

Additional Context

I don't know how to run conda info with the GitHub Actions, but I think the link to the GitHub Actions will help: https://github.com/deepmd-kit-recipes/installer/actions/runs/8133687249/job/22225572458

[github-actions]

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

1. Verify that you can still reproduce the issue at hand
2. Comment that the issue is still reproducible and include:
   - What OS and version you reproduced the issue on
   - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!