test_hook_writes_to_stderr failure "/bin/sh command not found" about sceptre HOT 4 CLOSED

This test was added in PR #1372, do you know anything about it @iainelder ?

from sceptre.

Yes, I added it. Not sure why it would fail. I'll take a look tomorrow!

from sceptre.

To follow your repro I need to install pyenv. I'll figure out how to do that this week.

What do you see when you skip the pyenv command and run poetry run tox -e py39?

For me, all the tests pass in tox's py39 environment.

from sceptre.

Your /bin/sh points to Bash. (It looks like your system is macOS.)

My /bin/sh points to Dash. My system is Ubuntu 20.

The shells write different error messages when they can't find the command.

• Bash: /bin/bash: missing_command: command not found
• Dash: /bin/dash: 1: missing_command: not found

The test expects /bin/sh to write Dash's error message.

Your /bin/sh writes Bash's error message, and so the test fails.

All I want to test here is that the hook writes to the standard error stream.

I think I should rewrite it so that it no longer depends on system-defined side effects of a missing command.

A simpler test would just echo text to the standard error stream and check that the same text comes out.

from sceptre.