Make it easier to run the StressTest script. (#1332)

Author: wil93

.gitignore

@@ -15,3 +15,4 @@ log/
 .vagrant/
 codecov/
 .dev/
+test_logs/

_cms-stresstest-internal.sh

@@ -0,0 +1,35 @@
+#!/usr/bin/env bash
+
+dropdb --host=testdb --username=postgres cmsdbfortesting
+createdb --host=testdb --username=postgres cmsdbfortesting
+cmsInitDB
+
+git clone https://github.com/cms-dev/con_test.git
+cd con_test
+
+# These don't play well with the StressTest script
+for i in communication communicationtwoways outputonly outputonlycomparator; do
+    sed -i "/$i/d" contest.yaml
+done
+
+# Take the solution.c, solution.py, etc, files from each task, and rename them
+# to taskname.c, taskname.py, etc. This is needed because the StressTest script
+# needs the solution name to match the submission format (task name).
+mkdir -p stress_sols
+for i in batch batch_comparator batch_file batchgrader batchwithoutgen; do
+    for j in $(ls -d $i/sol/*); do
+        ext=${j##*.}
+        cp $j stress_sols/${i%/}.$ext
+    done
+done
+
+cmsImportUser --all
+cmsImportContest --import-tasks .
+
+cd ..
+
+# Start ResourceService
+cmsResourceService -a 1 &
+sleep 5
+
+python3 cmstestsuite/StressTest.py --contest-id 1 --submissions-path stress_sols/

cms-stresstest.sh

@@ -0,0 +1,6 @@
+#!/usr/bin/env bash
+set -x
+
+GIT_BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD)
+
+docker compose -p $GIT_BRANCH_NAME -f docker-compose.test.yml run --build --rm stresstestcms

docker-compose.test.yml

@@ -19,3 +19,13 @@ services:
     privileged: true
     cgroup: host
     command: wait-for-it testdb:5432 -- ./_cms-test-internal.sh
+
+  stresstestcms:
+    build: .
+    depends_on:
+      - "testdb"
+    environment:
+      CMS_CONFIG: /usr/local/etc/cms-testdb.conf
+    privileged: true
+    cgroup: host
+    command: wait-for-it testdb:5432 -- ./_cms-stresstest-internal.sh

docs/Docker image.rst

@@ -7,15 +7,25 @@ dependencies. We also provide:
 
 * :gh_blob:`cms-test.sh`: This file uses :gh_blob:`docker-compose.test.yml` to
      spawn a volatile database (not persisted on disk) as well as a CMS instance
-     that automatically runs all tests.
+     that automatically runs all unit tests and functional tests.
+
+* :gh_blob:`cms-stresstest.sh`: Similar to `cms_test.sh` but runs the stress
+     tests instead of the unit tests. The stress test consists of: creating a
+     database, populating it with some sample tasks, and then simulating some
+     users logging in via ContestWebServer and repeatedly performing actions
+     such as download task statements and submitting solutions.
 
 * :gh_blob:`cms-dev.sh`: This file uses :gh_blob:`docker-compose.dev.yml` to
-     spawn a database (persisted in the local ``.dev/postgres-data`` folder
-     within the repository) as well as a CMS instance that only runs `bash`,
-     leaving you with a shell from where you can start cms services and servers.
-     The DB port and CMS server ports are also automatically forwarded on the
-     host machine (respectively to ``15432`` for the database, and ``8888-8890``
-     for CMS).
+     spawn a database (**persisted** in the local ``.dev/postgres-data`` folder
+     within the repository) as well as a CMS container that only runs `bash`,
+     leaving you with a shell from where you can start cms services. Changes
+     made in the repository are also reflected directly inside the container
+     (the source code is mounted as a docker volume). The DB port and CMS server
+     ports are also automatically forwarded on the host machine (respectively to
+     ``15432`` for the database, and ``8888-8890`` for CMS), which allows you to
+     access the CMS web server from your host machine, but that also means you
+     can only use `./cms-dev.sh` for one git branch at a time, as the ports are
+     already in use.
 
 Make sure that you have a recent version of Docker installed, as well as Docker
 Compose.