When one runs `test_syscall` on default configured MacOS test fails with unclear error message:

ivan.kochin@M-KXJQD73J73 build % sudo ctest -R test_syscall --output-on-failure
Password:
Test project /Users/ivan.kochin/work/git/wiredtiger/build
    Start 107: test_syscall


1/1 Test #107: test_syscall .....................***Failed    0.67 sec
test/syscall/wt2336_base/base.run:57: expecting OUTPUT("--------------wiredtiger_open");
test/syscall/WT_TEST.wt2336_base.0/stderr.txt:1: does not match
  1: dtrace: system integrity protection is on, some features will not be available


For a HOW TO on debugging, see the top of syscall.py
running /Users/ivan.kochin/work/git/wiredtiger/build/test/syscall/test_wt2336_base
comparing:
  test/syscall/wt2336_base/base.run
  test/syscall/WT_TEST.wt2336_base.0/stderr.txt
************************ FAILED ************************
  see results in /Users/ivan.kochin/work/git/wiredtiger/build/test/syscall/WT_TEST.wt2336_base.0






0% tests passed, 1 tests failed out of 1


Total Test time (real) =   0.67 sec


The following tests FAILED:
	107 - test_syscall (Failed)
Errors while running CTest 

This happens because this test executes `dtruss` tool to trace all the system calls performed by WT and it shows message that it cannot collect this info because of Apply System Integrity Protection (SIP) that was introduced as a part of OS X El Capitan (https://support.apple.com/en-us/102149). This error message is "dtrace: system integrity protection is on, some features will not be available". So this test which expects some other output from the binary execution just gets this error message and reports that the output is unexpected.

Generally speaking that means that average MacOS user without disabled SIP would receive unclear test failure by execution of standard WT test pool (eg. running ctest without arguments). And from my personal point of view this case should not be considered as a test failure since it doesn't show whether product broken or not. It shows just that user who executes it doesn't have enough permission to collect all the information that is required for this test.

Steps to reproduce:

• Configure and build WT on MacOS with enabled SIP (enabled by default)
• Run `ctest -R test_syscall`

Fix proposal:

• Run `dtruss` for some tool as a prerequisite check stage before running the actual test and report this test as skipped if `dtruss` fails (probably worth to print some message about why this test was skipped)

Definition of done:

• This case doesn't cause unclear error message and shows clear and descriptive picture of what happened to user.