bleedingdeacons / fellowship

91%

LAST BUILD ON BRANCH main

branch: SELECT

CHANGE BRANCH

x

Sync Branches

• No branch selected
• chore/build-quality-parity-with-reach
• chore/declare-php-extensions
• docs/tests-badge
• feat/admin-password-reset
• feat/admin-send-credits-author
• feat/all-gsrs
• feat/delivery-receipts
• feat/descriptive-user-agent
• feat/directory-cli
• feat/directory-group-and-gsr
• feat/directory-has-device
• feat/directory-service-position
• feat/drop-logging-route
• feat/identity-broker
• feat/initial-implementation
• feat/microsoft-and-facebook-sign-in
• feat/mixed-audiences
• feat/php-84-wp-711
• feat/remote-logging-config
• feat/reply-sender-id
• feat/say-when-a-handset-can-only-poll
• feature/differentiate-refusal
• feature/reauthenticate-key-rotation
• fix/clear-unregistered-push-token
• fix/device-cap-race
• fix/inbox-walks-forward
• fix/ios-envelope-in-apns-payload
• fix/release-push-retry
• fix/seal-on-read-claims
• fix/triage-semgrep-false-positives
• fix/unslash-the-settings-post
• main
• refactor/shared-password-store
• test/apple-sign-in-coverage
• test/coverage-repositories
• test/coverage-to-92
• test/link-load-plan
• test/pest-5

Build # 37090476896

Build Type

push

github

Committed by web-flow

Commit Message

test(load): add a JMeter plan for Link's read path and a seeder for it (#37)

What a handset asks Fellowship for once a message has reached it: the
launch push-token call, the sync that collects it again (the poll mark
only moves on a poll, from Link 1.29.1), the received acknowledgement, the
mark-read and the sync on returning to the list. Plus the push that never
arrived, the first sync after upgrading to 1.29.1 (up to ten pages of
fifty, walked the way MessageService.SyncAsync does), and a baseline that
boots WordPress and is refused before any query, so the difference is
Fellowship's own work.

seed-link-load.php mints devices for real members and writes messages
straight through the repositories, so nothing is pushed; reset and cleanup
undo it. Seed a local or test site only.

Run against the local site on 2026-10-03: unloaded, a request costs about
430 ms of WordPress boot and Fellowship adds 30-60 ms; a page of 50 sealed
messages costs about 100 ms over the boot; twenty first syncs over a
minute finished inside 70 s with no errors.

Coverage Stats

3573 of 3930 relevant lines covered (90.92%)

7.39 hits per line