#685 test_sem failing with wxGTK3

[Orion Poplawski]

I switched the Fedora build to use wxGTK3 and now test_sem.pro appears to be failing:

144: Test command: /builddir/build/BUILD/gdl-0.9.6/build/testsuite/launchtest "test_sem.pro"
144: Test timeout computed to be: 9.99988e+06
144: Xlib: extension "RANDR" missing on display ":99".
144: % Compiled module: TEST_SEM.
144: % Warning: UNIT keyword to SPAWN may not yet be fully implemented (proceeding)
144: -- background process:
144: Xlib: extension "RANDR" missing on display ":99".
144: <Expression> INT =
144: -- foreground process:
144: STATUS INT = 1
144: STATUS INT = 0
144: STATUS INT = 1
144: Test command: /builddir/build/BUILD/gdl-0.9.6/build/testsuite/launchtest "test_sem.pro"
144: Test timeout computed to be: 9.99988e+06
144: % Compiled module: TEST_SEM.
144: % Warning: UNIT keyword to SPAWN may not yet be fully implemented (proceeding)
144: -- background process:
144: % TEST_SEM: End of file encountered.
144: % Execution halted at: TEST_SEM 9 /builddir/build/BUILD/gdl-0.9.6/testsuite/test_sem.pro
144: % $MAIN$
144: Magick: abort due to signal 11 (SIGSEGV) "Segmentation Fault"...
144: TEST EXITED FROM SIGNAL 6

[Orion Poplawski]

Hmm, I think that's two different test runs.

Running by hand:

% Compiled module: TEST_SEM.
% Warning: UNIT keyword to SPAWN may not yet be fully implemented (proceeding)
-- background process:
% TEST_SEM: End of file encountered.
% Execution halted at: TEST_SEM 9 /builddir/build/BUILD/gdl-0.9.6/testsuite/test_sem.pro
% $MAIN$
Magick: abort due to signal 11 (SIGSEGV) "Segmentation Fault"...
TEST EXITED FROM SIGNAL 6

[Sylwester Arabas]

Orion, I'm clsing this one as hard to reproduce - if it would reoccur, please post a report with a backtrace on github. Thanks!