SeanCurtis-TRI
commented
1 year ago The timeout documented above occurred while working on #598. Simply retriggering the single failed test was enough to get it to pass.
However, the post merge CI check had a corresponding failure. This time in test_fcl_sphere_capsule:
75>PostBuildEvent:
setlocal
"C:\Program Files (x86)\CMake\bin\cmake.exe" -D TEST_TARGET=test_fcl_sphere_capsule -D TEST_EXECUTABLE=C:/projects/fcl/build/test/Release/test_fcl_sphere_capsule.exe -D TEST_EXECUTOR= -D TEST_WORKING_DIR=C:/projects/fcl/build/test -D TEST_EXTRA_ARGS= -D TEST_PROPERTIES= -D TEST_PREFIX= -D TEST_SUFFIX= -D NO_PRETTY_TYPES=FALSE -D NO_PRETTY_VALUES=FALSE -D TEST_LIST=test_fcl_sphere_capsule_TESTS -D CTEST_FILE=C:/projects/fcl/build/test/test_fcl_sphere_capsule[1]_tests.cmake -D TEST_DISCOVERY_TIMEOUT=5 -P "C:/Program Files (x86)/CMake/share/cmake-3.16/Modules/GoogleTestAddTests.cmake"
if %errorlevel% neq 0 goto :cmEnd
:cmEnd
endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
:cmErrorLevel
exit /b %1
:cmDone
if %errorlevel% neq 0 goto :VCEnd
:VCEnd
CMake Error at C:/Program Files (x86)/CMake/share/cmake-3.16/Modules/GoogleTestAddTests.cmake:40 (message):
Error running test executable.
Path: 'C:/projects/fcl/build/test/Release/test_fcl_sphere_capsule.exe'
Result: Process terminated due to timeout
Output:
The problem may be the antiquated compiler platform. Possibly need to update the build target in appveyor.
In windows CI (on appveyor), the
test_fcl_simpletest has been known to timeout (see reproduced log below).Generally, the test has issues; it is not a proper test. Here is a list of defects immediately obvious upon initial read (the list is not comprehensive):
Vectorn<S, N>is just an alias forEigen::Matrix<S, N, 1>, but we test all the matrix operations).So, while it's not immediately obvious what would be causing the timeouts, it seems safe to say that some clean up is due. The clean up may assist in time out problem (and certainly couldn't hurt).