ctest 10 minute timeout introduced between 3.31.0 and 4.1.0?

[Markus87]

ctest -T test -R SomeTest --debug
3.31.0: CTest\cmCTestRunTest.cxx:836 247: Test timeout computed to be: 10000000

4.10.0: Test timeout computed to be: 600

I checked the offending source code and did some debugging, but the 10 minutes have been there in 3.31.0 too, something else must have changed.

Does anyone have any link to the documentation for the 10 minutes default timeout? I have found nothing.

Whats also curious --timeout 0 is ignored if added. (values > 0 are not ignored)
If I remove -T test the 10 minutes timeout goes away.

What do you think, worth opening an issue?

[brad.king]

Cc: @purpleKarrot

Thanks. This bisects to CMake MR 9881. It doesn’t look intentional.

Please open an issue.

[brad.king]

@Markus87

ctest -T test -R SomeTest --debug

For reference, -T test is meant to activate dashboard client mode, which isn’t something normally done during local development.

[craig.scott]

@brad.king

For reference, -T test is meant to activate dashboard client mode, which isn’t something normally done during local development.

I believe at least one major IDE uses ctest -T test to run or query the set of defined tests. I don’t know why they chose to do that.

[Markus87]

Thanks!
This runs on our jenkins with the xUnit plugin, -T test was part of an example I used to get it to work.

[Markus87]

https://gitlab.kitware.com/cmake/cmake/-/issues/27139

[brad.king]

@craig.scott

at least one major IDE uses ctest -T test to run or query the set of defined tests.

Yes. See vscode-cmake-tools issue 4336, discourse topic [4.0.0 rc2] - "There was an error running ctest to determine available test executables", CMake Issue 26743, and CMake MR 10432.