chore: try test_release with multicore-sdr again

Author: vmx

.github/workflows/ci.yml

@@ -74,19 +74,20 @@ jobs:
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
 
-      - name: Test in release profile
-        run: |
-          #cargo test --verbose --release --workspace --all-targets ${{ matrix.cargo-args }}
-          # Run sequentially due to core assignment tests that otherwise might
-          #  interfere with each other
-          #cargo test --release -p storage-proofs-porep --features isolated-testing ${{ matrix.cargo-args }} -- --test-threads=1
-          # Getting the cores does not work on GitHub Actions, hence skip that
-          # specific test.
-          cargo test --release -p storage-proofs-porep --features isolated-testing ${{ matrix.cargo-args }} -- --skip stacked::vanilla::cores::tests::test_checkout_cores
-          # Some `storage-proofs-update` tests need to run sequentially due to
-          # their high memory usage.
-          #cargo test --release -p storage-proofs-update --features isolated-testing ${{ matrix.cargo-args }} -- --test-threads=1
-          cargo test --release -p storage-proofs-update --features isolated-testing ${{ matrix.cargo-args }}
+      - name: Run usual tests in release profile
+        run: cargo test --verbose --release --workspace --all-targets ${{ matrix.cargo-args }} -- --nocapture
+      - name: Run isolated PoRep tests in release profile
+        # Run sequentially due to core assignment tests that otherwise might
+        #  interfere with each other
+        #cargo test --release -p storage-proofs-porep --features isolated-testing ${{ matrix.cargo-args }} -- --test-threads=1
+        # Getting the cores does not work on GitHub Actions, hence skip that
+        # specific test.
+        run: cargo test --release -p storage-proofs-porep --features isolated-testing ${{ matrix.cargo-args }} -- --nocapture --skip stacked::vanilla::cores::tests::test_checkout_cores
+      - name: Run isolated update tests in release profile
+        # Some `storage-proofs-update` tests need to run sequentially due to
+        # their high memory usage.
+        #cargo test --release -p storage-proofs-update --features isolated-testing ${{ matrix.cargo-args }} -- --test-threads=1
+        run: cargo test --release -p storage-proofs-update --features isolated-testing ${{ matrix.cargo-args }} -- --nocapture
 
   #test_ignored_release:
   #  runs-on: ubuntu-latest
@@ -120,16 +121,25 @@ jobs:
   #    - name: Test ignored in release profile
   #      run: cargo test --release --workspace --no-default-features
   #
-  #build_gpu:
-  #  runs-on: ubuntu-latest
-  #  name: Build with CUDA and OpenCL support enabled
-  #  steps:
-  #    - uses: actions/checkout@v4
-  #    - name: Install required packages
-  #      run: sudo apt install --no-install-recommends --yes libhwloc-dev nvidia-cuda-toolkit ocl-icd-opencl-dev
-  #
-  #    - name: Test ignored in release profile
-  #      run: cargo build --workspace --features cuda,opencl
+
+  # TODO test GPU target
+       #- name: SupraSeal filecoin-proofs tests in release profile
+       #  run: |
+       #    cargo test -p filecoin-proofs --release --no-default-features --features cuda-supraseal -- --nocapture --test-threads=1
+       #    cargo test -p filecoin-proofs --release --no-default-features --features cuda-supraseal -- --nocapture --test-threads=1 --ignored
+
+  build_gpu:
+    runs-on: ubuntu-latest
+    name: Build with various GPU support enabled
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install required packages
+        run: sudo apt install --no-install-recommends --yes libhwloc-dev nvidia-cuda-toolkit ocl-icd-opencl-dev
+
+      - name: Build with `cuda` and `opencl` features enabled
+        run: cargo build --workspace --features cuda,opencl
+      - name: Build with `cuda-supraseal` feature enabled
+        run: cargo build --workspace --no-default-features --features cuda-supraseal
 
   #multicore_sdr:
   #  runs-on: ubuntu-latest