fix(e2e): give occ a maxBuffer so the worker scenarios stop self-skipping - #3304
Merged
Merged
Conversation
…ping background-job:list prints every job's serialized argument in one table; on a live instance that is 1.8 MiB, past Node's 1 MiB execSync default. The overflow threw, runWorkerJobId() caught it into null, and the worker-driven scenarios skipped as 'occ not reachable' while occ was fine. With the buffer raised, 'completing a task from the inbox advances its flow run' runs and passes on the dossiq proof instance.
Contributor
Quality Report — ConductionNL/openregister @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| check-specs | ✅ | ||||
| test-l10n | ✅ | ||||
| test-l10n-parity | ✅ | ||||
| format | ✅ | ||||
| check-schema-l10n | ✅ | ||||
| check-l10n-js | ✅ | ||||
| composer | ✅ | ✅ 174/174 | |||
| npm | ✅ | ✅ 543/543 | |||
| app:check-code | ⏭️ | ||||
| info.xml | ✅ | ||||
| REUSE | ❌ | ||||
| PHPUnit | ✅ | ||||
| Newman | ✅ | ||||
| Playwright | ⏭️ deferred — runs on the promotion into beta/main, not on a pull request into development | ||||
| Hydra gates | ✅ |
Quality workflow — 2026-09-01 19:47 UTC
Download the full PDF report from the workflow artifacts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On a live instance
occ background-job:listprints 1.8 MiB (every job's serialized argument), past Node's 1 MiBexecSyncdefault. The overflow threw,runWorkerJobId()caught it intonull, and the worker-driven scenarios offlow-user-task.spec.tsself-skipped as occ not reachable while occ was fine — a skip that reads as an environment limitation instead of a lost scenario.One change: the
occ()helper passesmaxBuffer: 32 MiB.Verified on the dossiq proof instance (8614): before the fix, scenario 3 ('completing a task from the inbox advances its flow run') skipped on every run; after it, the scenario runs and passes, including the worker half. Found during the 2026-09-01 dossiq case-flow acceptance run.
🤖 Generated with Claude Code