AutoBE
    Preparing search index...

    Interface IPhaseRuntime

    Compact digest of a realize-phase runtime execution result.

    Captures whether the generated backend actually booted and passed its e2e tests, independent of whether the TypeScript compilation succeeded. Two shapes are represented:

    • Normal execution: total / passed / failed populated, reason absent
    • Setup/infra failure (e.g. pnpm install, build:prisma, build:test crashed before any operation ran): total / passed / failed are 0 and reason describes the classification.
    interface IPhaseRuntime {
        elapsed: number;
        failed: number;
        passed: number;
        reason?: "rate_limit" | "unknown" | "aborted_stagnation" | "aborted_budget";
        reset?: boolean;
        simultaneous?: number;
        success: boolean;
        total: number;
    }
    Index

    Properties

    elapsed failed passed reason? reset? simultaneous? success total

    Properties

    elapsed: number

    Wall-clock duration from runtime start to completion, in ms.

    failed: number

    Number of operations whose error field is non-null.

    passed: number

    Number of operations whose error field is null.

    reason?: "rate_limit" | "unknown" | "aborted_stagnation" | "aborted_budget"

    Optional failure classification for infra-level errors. Uses the same tags as IPhaseState.reason.

    reset?: boolean

    Whether the database was reset before execution, when known.

    simultaneous?: number

    Concurrent execution limit used, when known.

    success: boolean

    True when setup completed and every executed operation produced no error (failed === 0 && total > 0). False for any infra failure or partial failure.

    total: number

    Number of e2e operations executed. 0 when setup failed.

    Settings

    Member Visibility

    On This Page

    Properties