From fa0fb50d8013977155d6324dd869c6f6cb03d7b7 Mon Sep 17 00:00:00 2001
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
Date: Tue, 27 Jun 2023 17:31:10 +0100
Subject: [PATCH] CI: run a normal all-features-test

I think we do actually do this as part of the coverage job, but that's
not really very clear (and getting the report in that job may be
annoying).

We also do it on nightly as part of the nightly test, but that's an
"allow_fail".
---
 .gitlab-ci.yml | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 21697c7f5..e5cd6bd5d 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -318,6 +318,23 @@ integration-shadow:
     - amd64
     - tpa
 
+rust-latest-test-all-features:
+  stage: test
+  image: rust:latest
+  script:
+    - rustup show
+    - cargo build --target x86_64-unknown-linux-gnu --locked --workspace --all-features --all-targets
+    - cargo test --target x86_64-unknown-linux-gnu --locked --workspace --all-features
+  after_script:
+    - ./maint/preserve target/x86_64-unknown-linux-gnu/debug/arti target/x86_64-unknown-linux-gnu/release/arti-bench
+    - cargo clean
+  artifacts:
+    paths:
+      - artifacts
+    expire_in: 1 hours
+  tags:
+    - amd64
+
 every-crate:
   stage: test
   image: rust:latest