Use release builds in CI

Author: Mark-Simulacrum

.github/workflows/ci.yml

@@ -18,11 +18,6 @@ jobs:
       - name: Ensure there are no warnings with Clippy
         run: cargo clippy --all -- -Dwarnings
 
-      - name: Check if the configuration is correct
-        run: |
-          cargo run -- create-lists
-          cargo run -- check-config
-
   test:
     name: Testing
     strategy:
@@ -41,13 +36,13 @@ jobs:
 
       - name: Build Crater
         shell: bash
-        run: cargo build
+        run: cargo build --release
 
       - name: Run Crater tests
         shell: bash
         run: |
-          cargo run -- create-lists
-          cargo test
+          cargo run --release -- create-lists
+          cargo test --release
 
   minicrater:
     name: Minicrater
@@ -64,8 +59,8 @@ jobs:
       - name: Run minicrater
         shell: bash
         run: |
-          cargo run -- create-lists
-          cargo test -- --ignored --nocapture --test-threads 1
+          cargo run --release -- create-lists
+          cargo test --release -- --ignored --nocapture --test-threads 1
         env:
           MINICRATER_FAST_WORKSPACE_INIT: 1
           MINICRATER_SHOW_OUTPUT: 1

.github/workflows/pr.yml

@@ -17,11 +17,6 @@ jobs:
       - name: Ensure there are no warnings with Clippy
         run: cargo clippy --all -- -Dwarnings
 
-      - name: Check if the configuration is correct
-        run: |
-          cargo run -- create-lists
-          cargo run -- check-config
-
   test:
     name: Linux testing
     runs-on: ubuntu-latest
@@ -32,12 +27,16 @@ jobs:
         run: rustup update nightly && rustup default nightly
 
       - name: Build Crater
-        run: cargo build
+        run: cargo build --release
+
+      - name: Check if the configuration is correct
+        run: |
+          cargo run --release -- create-lists
+          cargo run --release -- check-config
 
       - name: Run Crater tests
         run: |
-          cargo run -- create-lists
-          cargo test
+          cargo test --release
 
   # Note: this job is used so that there is a job named "conclusion" both in the PR and merge queue
   # CI. Otherwise, it would not be possible for PR CI to succeed.