Made LARGE runtime configurable in versions.json.

scripts/cmake/test/AddTest.cmake

@@ -42,8 +42,6 @@
 #         the benchmark output directory.
 
 function (AddTest)
-    # settings
-    set(LARGE_RUNTIME 60)
 
     # parse arguments
     set(options DISABLED)
@@ -77,7 +75,7 @@ function (AddTest)
             ${AddTest_SOURCE_PATH}/${AddTest_EXECUTABLE_ARGS})
     endif()
 
-    if(${AddTest_RUNTIME} GREATER ${LARGE_RUNTIME})
+    if(${AddTest_RUNTIME} GREATER ${ogs.ctest.large_runtime})
         string(PREPEND AddTest_NAME "LARGE_")
     endif()
 

scripts/cmake/test/OgsTest.cmake

 function (OgsTest)
-    # settings
-    set(LARGE_RUNTIME 60)
 
     if(NOT OGS_BUILD_CLI OR NOT BUILD_TESTING)
         return()
@@ -23,7 +21,7 @@ function (OgsTest)
         set(OgsTest_RUNTIME 1)
     endif()
 
-    if(${OgsTest_RUNTIME} GREATER ${LARGE_RUNTIME})
+    if(${OgsTest_RUNTIME} GREATER ${ogs.ctest.large_runtime})
         string(APPEND OgsTest_NAME_WE "-LARGE")
     endif()
 

web/content/docs/devguide/testing/test-data.md

@@ -17,16 +17,16 @@ An executable test can be run with several *wrappers*, e.g. with `valgrind`, `me
 AddTest(
     NAME GroundWaterFlowProcess
     PATH Elliptic/quad_20x10_GroundWaterFlow
-    RUNTIME 35                                                        # optional
-    EXECUTABLE ogs                                                    # optional
+    EXECUTABLE ogs
     EXECUTABLE_ARGS quad_20x10_GroundWaterFlow.prj
+    RUNTIME 35                                                        # optional
     WRAPPER time                                                      # optional
     TESTER diff                                                       # optional
     DIFF_DATA quad_20x10_constMat0.mesh.vtu quad_20x10_left_right.gml # optional
 )
 ```
 
-Tests are then run with `make ctest` or for more verbose output with `ctest -VV` (you may also use other [ctest options](https://cmake.org/cmake/help/v3.4/manual/ctest.1.html)). If the checker has some errors they are displayed. `RUNTIME` specifies the typical runtime in seconds on an Intel Xeon E5-2680 v2 @ 2.80 GHz with 500 GiB RAM (`envinf1`). Tests with a `RUNTIME > 60` are considered `LARGE`-tests.
+Tests are then run with `make ctest` or for more verbose output with `ctest -VV` (you may also use other [ctest options](https://cmake.org/cmake/help/v3.4/manual/ctest.1.html)). If the checker has some errors they are displayed. `RUNTIME` specifies the typical runtime in seconds on an Intel Xeon E5-2680 v2 @ 2.80 GHz with 500 GiB RAM (`envinf1`). Tests with a `RUNTIME > {{< dataFile "versions.ctest.large_runtime" >}}` are considered `LARGE`-tests.
 
 The functionality is very flexible and more wrappers and checker can be added later on. e.g. for running some statistics on output files and comparing them with statistics from reference files.
 

web/data/versions.json

@@ -31,5 +31,8 @@
       "win": "5.13.2"
     },
     "ubuntu": "20.04"
+  },
+  "ctest": {
+    "large_runtime": 60
   }
 }