The RunCMake.CTestResourceAllocation test timed out because it’s known to take a long time to complete. Increasing the time limit with --timeout on ctest should make it pass. The rest of the failures are not expected. To get more verbose information, run ctest directly (instead of make test) with the -V flag (and the -R flag to filter the failed tests). Since you’re using the bootstrap script, you’ll need to run the built CTest in the bin directory:
RunCMake.CTestResourceAllocation runs cleanly with the longer timeout. Thank you @kyle.edwards
On the machine I’m building on my home directory is remote (an nfs4 mount), ~/Builds is a symbolic link to a different remote file system (nfs) on a different server. I think some of this might be relevant to some of the other errors. I’ve attached all the verbose logs, and my initial/limited analysis. If people think these should be raised as issues on GitLab let me know and I will create them.
When I get a chance I will try and move to a build path without the symbolic link…
//—
BuildDepends, fails the first time but passes the second. Timestamp granularity/mismatch on nfs file systems?
CTestCoverageCollectGCOV, No idea about this one.
RunCMake.CommandLine, bust paths due to the symbolic link?
RunCMake.install, the 5’th and 6’th components of the regex are swapped in the output (runpath <==> rpath_search).
RunCMake.IFacePaths_INCDIRS, No tests selected to be run?!?
RunCMake.CPack_RPM.SUGGESTS, no idea…
RunCMake.CPack_TGZ, missmatch in the expected paths. The …/…/…/…/…/…/…/…/…/…/ prefix for the path appears in one of the lines in the CTestCoverageCollectGCOV output, maybe both related to the symbolic link?