ci: merge main to release

.github/workflows/build.yml

@@ -137,9 +137,9 @@ jobs:
         echo "Running tests..."
         if [[ "x${{ github.event.inputs.ignoreLowerCoverage }}" == "xtrue" ]]; then
           echo "Lower coverage failures will be ignored."
-          ./ietf/manage.py test --validate-html-harder --settings=settings_postgrestest --ignore-lower-coverage
+          ./ietf/manage.py test --validate-html-harder --settings=settings_test --ignore-lower-coverage
         else
-          ./ietf/manage.py test --validate-html-harder --settings=settings_postgrestest
+          ./ietf/manage.py test --validate-html-harder --settings=settings_test
         fi
         coverage xml
 

.github/workflows/ci-run-tests.yml

@@ -45,7 +45,7 @@ jobs:
           exit 1
         fi
         echo "Running tests..."
-        ./ietf/manage.py test --validate-html-harder --settings=settings_postgrestest
+        ./ietf/manage.py test --validate-html-harder --settings=settings_test
         coverage xml
 
     - name: Upload Coverage Results to Codecov

.vscode/tasks.json

@@ -48,7 +48,7 @@
             "args": [
                 "${workspaceFolder}/ietf/manage.py",
                 "test",
-                "--settings=settings_postgrestest"
+                "--settings=settings_test"
             ],
             "group": "test",
             "presentation": {
@@ -68,7 +68,7 @@
             "args": [
                 "${workspaceFolder}/ietf/manage.py",
                 "test",
-                "--settings=settings_postgrestest",
+                "--settings=settings_test",
                 "--pattern=tests_js.py"
             ],
             "group": "test",

README.md

@@ -83,7 +83,7 @@ If VS Code is not available to you, in your clone, type `cd docker; ./run`
 
 Once the containers are started, run the tests to make sure your checkout is a good place to start from (all tests should pass - if any fail, ask for help at tools-develop@). Inside the app container's shell type:
 ```sh
-ietf/manage.py test --settings=settings_postgrestest
+ietf/manage.py test --settings=settings_test
 ```
 
 Note that we recently moved the datatracker onto PostgreSQL - you may still find older documentation that suggests testing with settings_sqlitetest. That will no longer work.
@@ -228,7 +228,7 @@ before activating a new release.
 
 From a datatracker container, run the command:
 ```sh
-./ietf/manage.py test --settings=settings_postgrestest
+./ietf/manage.py test --settings=settings_test
 ```
 
 > You can limit the run to specific tests using the `--pattern` argument.