On some setups the xvfb based unit testing fails with this line at the end of the test outout:
/usr/bin/xvfb-run: line 186: kill: (3923210) - No such process
one example:
http://cdash.mitk.org/testDetails.php?test=13813420&build=726603
On some setups the xvfb based unit testing fails with this line at the end of the test outout:
/usr/bin/xvfb-run: line 186: kill: (3923210) - No such process
one example:
http://cdash.mitk.org/testDetails.php?test=13813420&build=726603
rMITK MITK | |||
Restricted Differential Revision | rMITK1780784feb8e Fixed Qt test invocation | ||
Restricted Differential Revision | rMITKf06596f70f8d Fixed Qt test invocation | ||
Restricted Differential Revision | rMITKa93a881e0170 Make linux headless UI testing more configurable | ||
Restricted Differential Revision | rMITKeaa893583df1 Moved XVFB testing configuration to superbuild | ||
Restricted Differential Revision | rMITKe95eb8546215 Make linux headless UI testing more configurable |
Ok, on fedora there is a newer xvfb version which includes a new option for a more robust choice of a suitable display number which seems to fix the issue for me.
Unfortunately this option is not available on ubuntu 18.04.. To be a bit more future proof I would suggest to make the actual call to xvfb-run configurable via a CMake option and default this to the current value that works on Ubuntu