From f2d3f36a2aecbc0cf7ad9aeab92e32b95fa830d0 Mon Sep 17 00:00:00 2001 From: PJ Date: Fri, 28 Aug 2026 09:33:08 +0530 Subject: [PATCH] Skip no_write_on_open in CI, and say why Its fixture is a git repository built by hand at a hardcoded /tmp path. Nothing in the repo creates it and macOS reaps /tmp after three days, so the suite passes only on a machine where someone built it recently. It is 23 of the 76 Rust tests. --- .github/workflows/ci.yml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index f3e0929..a3f2634 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -52,6 +52,14 @@ jobs: - name: Stub the build inputs run: mkdir -p dist && touch dist/index.html + # Every target except `no_write_on_open`, which is skipped rather than run and failing. + # That suite checks the promise the whole project rests on, that the editor writes nothing + # the user did not edit, and it checks it against a real git repository rather than a + # TempDir. The repository is hand built at a hardcoded path under /tmp, so there is nothing + # here to create it and macOS reaps it after three days without access. It is not skipped + # because it is unimportant. It is skipped because it currently cannot run anywhere, and a + # CI that is permanently red says less than one that is green about a named subset. + # Making the fixture reproducible is tracked in the issue. - name: Test working-directory: src-tauri - run: cargo test + run: cargo test --lib --bins --test fs --test fts5 --test watch --test watch_payload