From 1c20e8445614534d682d360549826c5edf871ef5 Mon Sep 17 00:00:00 2001 From: Joshua Liebow-Feeser Date: Sun, 29 Mar 2026 19:24:29 +0000 Subject: [PATCH] [ci][hermes] Run integration tests gherrit-pr-id: Gr4qottxa22y4kfhk2a5vctnhsswyoiac --- .github/workflows/hermes.yml | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/.github/workflows/hermes.yml b/.github/workflows/hermes.yml index db295ac0d9..6ec1d24dcc 100644 --- a/.github/workflows/hermes.yml +++ b/.github/workflows/hermes.yml @@ -62,10 +62,22 @@ jobs: working-directory: tools/hermes run: cargo run --bin cargo-hermes -- setup - - name: Run tests + # Run unit tests separately, as they're much less likely to have bugs + # during local development, and this makes the GitHub Actions output + # easier to skim (in particular, it's clear at a glance whether a failure + # is due to unit or integration tests). + - name: Run unit tests working-directory: tools/hermes run: cargo test --verbose --bin cargo-hermes + # We duplicate running unit tests since they're very cheap compared to + # integration tests, and this way it's easier to be sure that we run all + # tests instead of specifically trying to carve out unit tests and risk + # missing test categories. + - name: Run all tests + working-directory: tools/hermes + run: cargo test --verbose + # Used to signal to branch protections that all other jobs have succeeded. all-jobs-succeed: # WARNING: This name is load-bearing! It's how GitHub's settings UI configures which jobs