Give this repository a pipeline, which it has never had #8

Merged
paulhitt merged 3 commits from ci/this-repo-has-never-had-a-pipeline into main 2026-09-07 00:58:54 +00:00
paulhitt commented 2026-09-07 00:13:32 +00:00 (Migrated from gitlab.com)

Both open merge requests show pipeline: None — not failed, not
skipped, never run. There was no .gitlab-ci.yml, so nothing has ever
tested a change to the service that holds people's files and is about to
start signing their sessions. !1 has been open since 23 August waiting
for a verdict that could not arrive.

Two jobs, because the two suites answer different questions and
TESTING.md is right that neither answers the whole one: swift test
proves the lattice, the SQL and the accounts kit; the node suite proves
the client modules the browser runs. Whether a route or a button is wired
to any of it is what the integration scripts are for, and those need a
live stack, so they stay manual.

Both gates assert on COUNTS rather than on exit status:

  • The package builds three separate test bundles. A target that
    silently stopped being built would take its tests with it, and the
    remaining bundles would still report a clean run. The gate sums the
    per-bundle totals and floors them at 68 against today's 75.
  • node --test client/test/ — the directory rather than the glob —
    runs NOTHING and reports one opaque failure. I verified that rather
    than taking TESTING.md's word for it, because a warning nobody has
    checked is how the last one I wrote turned out to be false. The glob
    matching too little is the same failure in the other direction, so
    the count is floored at 85 against today's 95.

⚠️ One thing I could not pin down and will not paper over: the very first
node run in a fresh container reported 94 passed and 1 failed, and I have
not reproduced it in nine subsequent runs, six warm and three cold. No
subtest was marked failing in that output — every one of the 95 said ok —
so the failure was at file level. If this job goes red intermittently
that is the thing to chase, and the count gate will show it as 94 rather
than as a vague red.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

Both open merge requests show `pipeline: None` — not failed, not skipped, never run. There was no `.gitlab-ci.yml`, so nothing has ever tested a change to the service that holds people's files and is about to start signing their sessions. !1 has been open since 23 August waiting for a verdict that could not arrive. Two jobs, because the two suites answer different questions and TESTING.md is right that neither answers the whole one: `swift test` proves the lattice, the SQL and the accounts kit; the node suite proves the client modules the browser runs. Whether a route or a button is wired to any of it is what the integration scripts are for, and those need a live stack, so they stay manual. Both gates assert on COUNTS rather than on exit status: - The package builds three separate test bundles. A target that silently stopped being built would take its tests with it, and the remaining bundles would still report a clean run. The gate sums the per-bundle totals and floors them at 68 against today's 75. - `node --test client/test/` — the directory rather than the glob — runs NOTHING and reports one opaque failure. I verified that rather than taking TESTING.md's word for it, because a warning nobody has checked is how the last one I wrote turned out to be false. The glob matching too little is the same failure in the other direction, so the count is floored at 85 against today's 95. ⚠️ One thing I could not pin down and will not paper over: the very first node run in a fresh container reported 94 passed and 1 failed, and I have not reproduced it in nine subsequent runs, six warm and three cold. No subtest was marked failing in that output — every one of the 95 said ok — so the failure was at file level. If this job goes red intermittently that is the thing to chase, and the count gate will show it as 94 rather than as a vague red. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
paulhitt commented 2026-09-07 00:13:32 +00:00 (Migrated from gitlab.com)

assigned to @paulhitt

assigned to @paulhitt
paulhitt commented 2026-09-07 00:35:33 +00:00 (Migrated from gitlab.com)

added 1 commit

  • 426d843f - The test suite did not compile on the platform the service runs on

Compare with previous version

added 1 commit <ul><li>426d843f - The test suite did not compile on the platform the service runs on</li></ul> [Compare with previous version](/paulhitt/flamenet-files/-/merge_requests/8/diffs?diff_id=2007843206&start_sha=a95a64cde9b0ce53bdf081e94ba4c3480699d5d1)
paulhitt commented 2026-09-07 00:52:34 +00:00 (Migrated from gitlab.com)

added 1 commit

  • e738a2ea - The gate was written in python, and the Swift image has no python

Compare with previous version

added 1 commit <ul><li>e738a2ea - The gate was written in python, and the Swift image has no python</li></ul> [Compare with previous version](/paulhitt/flamenet-files/-/merge_requests/8/diffs?diff_id=2007851873&start_sha=426d843f5ea1e5ea7bd17307e939417e6569eddd)
paulhitt commented 2026-09-07 00:58:55 +00:00 (Migrated from gitlab.com)

mentioned in commit 3c635735d0

mentioned in commit 3c635735d01a5e2816263a84fdeb06a3d1a1d372
paulhitt (Migrated from gitlab.com) merged commit 3c635735d0 into main 2026-09-07 00:58:55 +00:00
paulhitt commented 2026-09-21 21:01:52 +00:00 (Migrated from gitlab.com)

mentioned in merge request flamenet-messenger-android!141

mentioned in merge request flamenet-messenger-android!141
paulhitt commented 2026-09-21 21:01:53 +00:00 (Migrated from gitlab.com)

mentioned in merge request flamenet-messenger-ios!217

mentioned in merge request flamenet-messenger-ios!217
This repo is archived. You cannot comment on pull requests.
No Reviewers
No labels
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: extant2000/flamenet-files#8