Add vsoch + add tests?

[ngam]

@vsoch (as per discussion in singularityhub/singularity-hpc#464) I had some of these tests in earlier iterations, but there were issues here and there. I am happy to add them again in this pr to assess how best to approach this.

    ## possible tests to run to ensure qc?
#     - pytest shpc/tests/test_settings.py  # [not win]
#     ## ignore linux test because test returns verbose value
# #     - pytest shpc/tests/test_utils.py  # [not linux64]
#     - pytest shpc/tests/test_container_config.py  # [not win] 
#     ## ignore othere tests because they trigger docker/singularity/podman

---

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[ngam]

@conda-forge-admin, please rerender

[vsoch]

@ngam with respect to testing, my thinking for conda recipes is that the minimal test is just to do shpc --version (or version). Personally speaking I think shpc (at its repo) should be the main test runner - especially the tests here that require container technologies / lmod / modules that would need to be installed. We can't easily do that here.

[ngam]

@ngam with respect to testing, my thinking for conda recipes is that the minimal test is just to do shpc --version (or version). Personally speaking I think shpc (at its repo) should be the main test runner - especially the tests here that require container technologies / lmod / modules that would need to be installed. We can't easily do that here.

Yes, that was exactly my rationale, see initial pr and discussion (with myself) here: conda-forge/staged-recipes#17085

[ngam]

And especially that the build is pretty similar, etc. testing here wouldn't really be all that valuable. We usually like to do rigorous tests for more involved builds --- did you know we build singularity/ce itself here too? I am also adding apptainer soon to stay up to date with the drama 🤦

https://github.com/conda-forge/singularity-feedstock
https://github.com/conda-forge/singularityce-feedstock

[ngam]

@vsoch, are you cool then with me merging this or would you like some more time to see if you'd like anything changed? Once merged, you will have the same access as me 😄

[vsoch]

I think it looks great - merge away!

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!