development's E2E has been red since 2026-08-28 08:10:37Z. Last green run: 2026-08-27 19:42:38Z.
✘ tests/e2e/spec-coverage/first-time-setup.spec.ts:77 › First-time setup contract › setup st…
Error: no organisation name is configured in CI
expect(received).toBe(expected)
Expected: false
Received: true
> 126 | ).toBe(false)
127 | expect(res.json.completed).toBe(true)
Three consecutive push runs on development fail identically: 33154306699 (08:10), 33157392918
(08:57), 33161715925 (10:01). dashboard.spec.ts fails alongside it in the later runs.
Not the flow-page migration, and not the 2.21 bump
Both are ruled out by timing, not by assumption:
|
|
| First failing run |
08:10:37 |
#1489 (flow pages + @conduction/nextcloud-vue 2.19 → 2.21) merged |
08:57:12 |
#1497 (duplicate demo-data step) merged |
09:40:10 |
The failure predates both. At 08:10 this app was still on 2.19 and still had its original manifest.
So whatever broke it landed between 19:42 on the 27th and 08:10 on the 28th.
Worth checking first
The assertion's own message — "no organisation name is configured in CI" — points at setup state
rather than at the UI: the spec expects an organisation NOT to be configured and finds one that is.
That reads like leaked or pre-seeded state rather than a rendering fault, which would also explain
why dashboard.spec.ts joins it in later runs.
Two candidates, both cheap to eliminate:
- a change to
tests/e2e/ci-seed.sh or global-setup.ts in that window
- a shared-workflow change consumed as
@main (several landed that morning)
Note for whoever picks this up
Do not read a cancelled run in this window as evidence either way — four of the runs between 09:38
and 10:00 are cancelled, and a cancelled run carries no verdict.
development's E2E has been red since 2026-08-28 08:10:37Z. Last green run: 2026-08-27 19:42:38Z.Three consecutive push runs on
developmentfail identically:33154306699(08:10),33157392918(08:57),
33161715925(10:01).dashboard.spec.tsfails alongside it in the later runs.Not the flow-page migration, and not the 2.21 bump
Both are ruled out by timing, not by assumption:
#1489(flow pages +@conduction/nextcloud-vue2.19 → 2.21) merged#1497(duplicatedemo-datastep) mergedThe failure predates both. At 08:10 this app was still on 2.19 and still had its original manifest.
So whatever broke it landed between 19:42 on the 27th and 08:10 on the 28th.
Worth checking first
The assertion's own message — "no organisation name is configured in CI" — points at setup state
rather than at the UI: the spec expects an organisation NOT to be configured and finds one that is.
That reads like leaked or pre-seeded state rather than a rendering fault, which would also explain
why
dashboard.spec.tsjoins it in later runs.Two candidates, both cheap to eliminate:
tests/e2e/ci-seed.shorglobal-setup.tsin that window@main(several landed that morning)Note for whoever picks this up
Do not read a
cancelledrun in this window as evidence either way — four of the runs between 09:38and 10:00 are cancelled, and a cancelled run carries no verdict.