SysprogsTestHooks write

[Jensa]

Hi,

I’m getting a whole bunch of: “==2217== Warning: invalid file descriptor -1 in syscall write()” from the SysprogsTestHooks.cpp when I run a Google UnitTest manually/outside VS without anything listening on the other end of the pipe when using valgrind.
Please add some protection to the write() call there to avoid that.

Also, it would be even better to have some preprocessor directive to be able to disable the entire SysprogsTestHooks logic to still easily be able to use the package but without having the additional layers always there when building tests that will not run in VS.

Regards
Jens Nilsson

[support]

Hi,

You can actually override this by setting the SYSPROGS_TEST_REPORTING_PIPE environment variable to /dev/null. This will suppress the warning and will make the test framework work pretty close to the original unpatched version.

[Jensa]

Thanks, that would work too I guess.

[Author]

Posts