Fix quality gate silently passing when historyPath is set (fixes #895 and #827) (closes #861) - #924

Context

Fixes #895 and #827 (closes #861).

When historyPath is configured, allure quality-gate exits with code 0 and prints nothing, no matter how many rules the results violate. The only trace it leaves is an allure-report/ directory containing a single test-results.json and no quality-gate.json, exactly as reported in the issue. allure generate and allure run hit the same defect; there it goes mostly unnoticed because the report has already been written by the time the process stalls.

Root cause. AllureLocalHistory opens streams on a FileHandle with autoClose: false and then awaits FileHandle.close() in a finally block without ever destroying them. Such streams are never destroyed on their own, and the handle stays referenced until they emit "close" — so FileHandle.close() waits for a reference that is never released and never settles. As a consequence AllureReport.done() never returns, the event loop drains, and Node exits with code 0 before the quality gate is ever validated.

This is why the issue looks like the config file is ignored: the reporter's config sets historyPath, while the --max-failures run they compared against was made without --config and therefore without history. Rule parsing was never the problem.

Note that running the CLI through yarn allure … hides the defect — Yarn PnP preloads .pnp.cjs, which shifts the timing enough for close() to settle. Under plain node / npx, which is what users run, it deadlocks. Vitest masks it as well. The numbers below come from a clean npm i [email protected] with the built history.js swapped in and run under plain node:

Changes.

• packages/core/src/history.ts — destroy every stream opened on the history file handle before closing it, in the order the streams were opened: destroying a reader that shares its handle with a still open writer never completes, whereas destroying the writer closes the reader along with it. Closing the handle tolerates EBADF, because a destroyed stream may already have closed the descriptor depending on the runtime.
• packages/cli/src/commands/qualityGate.ts — safety net: a quality gate must never pass silently. If the process is about to exit before the validation has finished, the command now reports it and exits with code 1 instead of leaving the caller with a successful exit code. Checked against the unfixed deadlock, it turns the silent exit 0 into a loud failure.

Tests.

• packages/core/test/history.streams.test.ts (new) — asserts that every stream opened on the history file handle is closed, for the new-file, existing-file and read paths. All three fail without the fix.
• packages/cli/test/commands/qualityGate.test.ts — two tests for the new safety net: it fires on an interrupted run and stays silent on a completed one.

yarn format:check, oxlint and the @allurereport/core (528) and allure (217) suites pass.

Checklist

• Sign Allure CLA
• Provide unit tests