CLI: Run (Test) Command Exits W/O Error When Wrapper Not Found

[dOrgJelli]

Describe the bug
When a polywrap run loads a polywrap.test.yaml manifest that includes a wrapper URI that is not resolvable (doesn't exist), the command seems to exit prematurely w/o any error message.

Please provide the steps to reproduce and if possible a minimal demo of the problem.

• Clone the toolchain repo
• Build packages (so CLI is present)
• cd ./packages/test-cases/cases/cli/run/001-yaml-workflow/
• make sure ./packages/test-cases/cases/cli/run/run-test-wrapper/build doesn't exist
• run ../../../../../cli/bin/polywrap run
• The command exits w/o any error:

001-yaml-workflow % ../../../../../cli/bin/polywrap run
🔄 Manifest loaded from ./polywrap.test.yaml
✅ Manifest loaded from ./polywrap.test.yaml

If you now go and build the run-test-wrapper wrapper, the run command will succeed.

Expected behavior
There should be an error stating that the wrapper cannot be found.

Relevant environment details:

• CLI Version: 0.9.3

[krisbitney]

I tried to reproduce the error on the origin-dev branch and I got this output. What do you think?

[dOrgJelli]

@krisbitney does this result in an exit code of non-zero?

[krisbitney]

@krisbitney does this result in an exit code of non-zero?

I looked into it and it doesn't, no.

Each step of each job is a distinct invocation. Some can fail while others succeed. So it makes sense that it works this way.