Tests: echo -n is not portable

[mtelka]

Some tests expects the echo command to support -n option. This is usually the case, but not always. Actually, the -n option for echo is not portable. Because of this some tests fails with errors like:

FAIL: test_no_interfere1 (tests.test.ExecutionContextTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "$(BUILD_DIR)/tests/test.py", line 3447, in test_no_interfere1
    self.assertEqual("TEST", out.getvalue())
AssertionError: 'TEST' != '-n TEST\n'
- TEST
+ -n TEST

Here is an example how various echo implementations works on OpenIndiana (and, AFAIK, on Solaris too):

$ /usr/bin/echo -n 123                             # Solaris/illumos echo
-n 123
$ /usr/ucb/echo -n 123                             # BSD echo
123$ /usr/gnu/bin/echo -n 123                      # GNU echo
123$

Yes, we do have three standalone echo implementations :-).

Documentation:

• POSIX echo
• Solaris/illumos echo implementation
• BSD-compatible echo implementation for Solaris/illumos

[mtelka]

Here is a full list of tests with this failure:

FAIL: test_basic (tests.test.ExecutionContextTests)
FAIL: test_set_in_parent_function (tests.test.ExecutionContextTests)
FAIL: test_no_interfere1 (tests.test.ExecutionContextTests)
FAIL: test_stringio_output (tests.test.FunctionalTests)

[mtelka]

Actually, this was fixed via 1f09994.

[amoffat]

Yes my mistake