sanitycheck: Execute binary in output directory

[vanwinkeljan]

Execute the test binary from the output directory instead of directory
where sanitycheck was started.

This will ensure that any artifact created with a relative path by the
test binary will be placed in the output directory instead of creating
the artifact in the directory where sanitycheck was executed and prevent
any possible conflicts.

One of the use case is the flash support for native posix (PR #12503) which
will create a binary file that stores the flash contents.

[marc-hb]

Looks good if you can confirm that:

• the case self.call_make_run = True has been tested at least once;
• '\n' is portable, and
• the verbose statement looks OK. Can you copy/paste a sample log output here?

[vanwinkeljan]

• the case self.call_make_run = True has been tested at least once;

It has been tested by running the crc unit test (see output bellow)

• '\n' is portable, and

No it is not, was a bit in a hurry and forgot to use os.linesep

• the verbose statement looks OK. Can you copy/paste a sample log output here?

Output for running native posix binary:

Spawning process: /srv/workspace/dxplore/zephyr/code/zephyr/tests/subsys/fs/fat_fs_api/sanity-out/native_posix/tests/subsys/fs/fat_fs_api/filesystem.fat/zephyr/zephyr.exe
Spawning process in directory: /srv/workspace/dxplore/zephyr/code/zephyr/tests/subsys/fs/fat_fs_api/sanity-out/native_posix/tests/subsys/fs/fat_fs_api/filesystem.fat
Spawning BinaryHandler Thread for native_posix/tests/subsys/fs/fat_fs_api/filesystem.fat

Output running unit tetst:

Spawning process: /srv/workspace/dxplore/zephyr/code/zephyr/tests/unit/lib/sanity-out/unit_testing/tests/unit/lib/crc/misc.crc/testbinary
Spawning process in directory: /srv/workspace/dxplore/zephyr/code/zephyr/tests/unit/lib/sanity-out/unit_testing/tests/unit/lib/crc/misc.crc
Spawning BinaryHandler Thread for unit_testing/tests/unit/lib/crc/misc.crc

[marc-hb]

I just spent more than a split second looking at this particular EOL situation. As usual with EOLs it's a mess:

• The verbose() function here uses '\n' anyway
• it started re-inventing python's logging module
• Python's documentation says: "Do not use os.linesep as a line terminator when writing files opened in text mode (the default); use a single '\n' instead, on all platforms."
• verbose() uses sys.stdout.write(). Does Python open sys.stdout in text mode? I don't know.

Let's not care. Let's leave those questions as a (search and replace) exercise for whoever will tackle the much bigger task of porting sanitycheck to Windows (#2664).