Skip to content

test: fix stale lockstep counts for #2184 semaphore sync (flag + job) - #2202

Merged
jung-thomas merged 1 commit into
DEVfrom
worktree-fix-lockstep-counts
Sep 8, 2026
Merged

test: fix stale lockstep counts for #2184 semaphore sync (flag + job)#2202
jung-thomas merged 1 commit into
DEVfrom
worktree-fix-lockstep-counts

Conversation

@jung-thomas

Copy link
Copy Markdown
Contributor

Problem

Unit tests failing on DEV (unit tests workflow, 4 failures):

  • test/unit/db-flags.test.js — expected 14 managed flags, got 15
  • test/unit/srv/scheduler-registry.test.js — expected 49 jobs, got 50

Root cause

PR #2197 (#2184 Semaphore taxonomy auto-sync) legitimately added:

  • SEMAPHORE_SYNC_ENABLED managed DB feature flag (srv/lib/feature-flags/registry.js)
  • semaphore-tag-sync scheduled job (srv/jobs/scheduler.js)

…but did not bump the two lockstep-counter assertions that guard those registries. Feature ships dark (default OFF), so only the test counters are stale — no product bug.

Fix

  • db-flags: 14 → 15 across all three count assertions + comment.
  • scheduler-registry: 49 → 50 + assert the new semaphore-tag-sync job name.

Both files green locally (17/17).

PR #2197 (#2184 Semaphore taxonomy auto-sync) added the
SEMAPHORE_SYNC_ENABLED managed DB flag and the semaphore-tag-sync
scheduled job but did not update the two lockstep-counter assertions,
breaking unit tests on DEV.

- db-flags.test.js: managed flag count 14 -> 15 (3 assertions)
- scheduler-registry.test.js: job count 49 -> 50 + assert the new
  semaphore-tag-sync job name
@jung-thomas
jung-thomas merged commit 814db56 into DEV Sep 8, 2026
2 of 3 checks passed
@jung-thomas
jung-thomas deleted the worktree-fix-lockstep-counts branch September 8, 2026 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant