add make test-full target; make test more focused

The benchmark and fuzz targets in particular take quite a long time to run, and are usually not the
focus of development. They're still worth running in CI, though, to catch bitrot.

Author: acfoltzer

.github/workflows/main.yml

@@ -14,7 +14,7 @@ jobs:
     # This action builds the container and executes the test suite inside it.
     - uses: ./.github/actions/test
       with:
-        target: test
+        target: test-full
 
     - name: Ensure testing did not change sources
       run: git diff --exit-code

Makefile

@@ -21,11 +21,10 @@ install-dev: build-dev
 	@helpers/install.sh --unoptimized
 
 .PHONY: test
-test: indent-check test-except-fuzz test-fuzz
+test: indent-check test-packages
 
-.PHONY: test-except-fuzz
-test-except-fuzz:
-	cargo build -p lucet-spectest # build but *not* run spectests to mitigate bitrot while spectests don't pass
+.PHONY: test-packages
+test-packages:
 	cargo test --no-fail-fast \
             -p lucet-runtime-internals \
             -p lucet-runtime \
@@ -35,6 +34,13 @@ test-except-fuzz:
             -p lucet-wasi \
             -p lucet-wasi-fuzz \
             -p lucet-validate
+
+.PHONY: test-full
+test-full: indent-check test-except-fuzz test-fuzz
+
+.PHONY: test-except-fuzz
+test-except-fuzz: test-packages
+	cargo build -p lucet-spectest # build but *not* run spectests to mitigate bitrot while spectests don't pass
 	cargo test --benches -p lucet-benchmarks -- --test # run the benchmarks in debug mode
 	helpers/lucet-toolchain-tests/signature.sh