Skip to content

fix(e2e): give occ a maxBuffer so the worker scenarios stop self-skipping #3304

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rubenvdlinde merged 1 commit into from
Sep 1, 2026
Merged

fix(e2e): give occ a maxBuffer so the worker scenarios stop self-skipping #3304

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions tests/e2e/api-direct/flow-user-task.spec.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,13 @@ function occ(args: string): string {
}
return execSync(`docker exec -u www-data ${CONTAINER} php occ ${args}`, {
encoding: 'utf8',
// `background-job:list` prints every job's serialized argument in one
// table; on a live instance that is well past Node's 1 MiB execSync
// default. The overflow throws ENOBUFS, the catch in runWorkerJobId()
// returns null, and the worker-driven scenarios self-skip as "occ not
// reachable" while occ is fine. Measured 1.8 MiB on a fresh proof
// instance, 2026-09-01.
maxBuffer: 32 * 1024 * 1024,
})
}

Expand Down
Loading