From 069b49b795d99a228fd3c9da79a8c010c3d7d02e Mon Sep 17 00:00:00 2001
From: Arthur Bit-Monnot <abitmonnot@laas.fr>
Date: Mon, 6 Jan 2025 17:46:04 +0100
Subject: [PATCH] ci(solver): run tests with different width in CI

---
 .github/workflows/aries.yml |  4 ++++
 justfile                    | 19 -------------------
 2 files changed, 4 insertions(+), 19 deletions(-)

diff --git a/.github/workflows/aries.yml b/.github/workflows/aries.yml
index 30f86dbd..60e7c6a0 100644
--- a/.github/workflows/aries.yml
+++ b/.github/workflows/aries.yml
@@ -15,6 +15,10 @@ jobs:
           fetch-depth: 0
       - uses: dtolnay/rust-toolchain@stable
       - run: cargo test
+      - name: Test with i64 int type
+        run: cargo test --features aries/i64
+      - name: Test with i128 int type
+        run: cargo test --features aries/i128
 
   lints:
     name: Rustfmt and Clippy
diff --git a/justfile b/justfile
index 180a9fa6..4934e855 100644
--- a/justfile
+++ b/justfile
@@ -4,7 +4,6 @@ set dotenv-load := true
 
 ci: ci-up-solve ci-up-val ci-ipc
 
-test: test-i32 test-i64 test-i128 test-i64_i128
 
 # Run planning tests for UP integration
 ci-up-solve:
@@ -29,21 +28,3 @@ up-export problem:
 # Solve specific IPC problems
 ipc-solve +problem:
     ARIES_UP_ASSUME_REALS_ARE_INTS=true python3 ci/ipc.py {{problem}}
-
-# Run tests using i32 as IntCst
-test-i32:
-    cargo test
-
-# Run tests using i64 as IntCst
-test-i64:
-    cargo test --features i64
-
-# Run tests using i128 as IntCst
-test-i128:
-    cargo test --features i128
-
-# Verify that aries doesn't build with both i128 and i64 features
-test-i64_i128:
-    @echo "checking i128 and i64 can't be enabled simultaneously"
-    if cargo test --features i128,i64; then echo "expected cargo test to fail when both i64 and i128 are enabled"; exit 1; fi
-    @echo "ok"
\ No newline at end of file