Major - P3 Sulabh Mahajan recently had a try of running wtperf_xray.sh without instrumenting with fxray-instrument. We have a check for this in the script but it didn't seem to work as intended. The output looked like this:
sulabh@sud:~/work/wt-dev/build_posix/bench/wtperf$ ../../../bench/wtperf/runners/wtperf_xray.sh runme.wtperf
|
../../../bench/wtperf/runners/wtperf_xray.sh: using WT_TEST as home directory
|
objdump: section 'xray_instr_map' mentioned in a -j option, but not found in any input file
|
../../../bench/wtperf/runners/wtperf_xray.sh: creating directory WT_TEST
|
rm: cannot remove 'xray-log.wtperf.*': No such file or directory
|
rm: cannot remove 'WT_TEST/wtperf_account.txt': No such file or directory
|
rm: cannot remove 'WT_TEST/wtperf_stack.txt': No such file or directory
|
rm: cannot remove 'WT_TEST/wtperf_graph.svg': No such file or directory
|
rm: cannot remove 'WT_TEST/wtperf_flame.svg': No such file or directory
|
ls: cannot access 'xray-log.wtperf.*': No such file or directory
|
../../../bench/wtperf/runners/wtperf_xray.sh: detected more than one xray log
|