Incident Dossier

The Failure That Disappeared In The Aggregate

A pipeline stage runs a sequence of steps. Some are critical (must stop the stage on failure); some are non-critical (their failures should be noted but the stage continues). With `continueOnError: true`, the failing step is correctly appended to the per-step list — but the stage's aggregate `ok` boolean never reflects that anything went wrong. Operators relying on the aggregate see a green pipeline, while the per-step log line for the failing step is the only signal — and only if anyone scrolls down to it.

Initial failing signalstage with continueOnError:true reports ok:true even when a step throwsExpected behavior: runStage({continueOnError:true, ...throwing step}).ok === false · actual behavior: runStage({continueOnError:true, ...throwing step}).ok === true

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Open src/pipeline.js. Trace what happens when a step throws inside the loop.
Note that the per-step record gets marked ok:false, but the stage aggregate is initialised once at the top and updated only in the non-continuable branch.
Update the aggregate in the continue-on-error branch so a single failed step flips the stage to ok:false.

Focus Mode

Start

src/pipeline.js

Likely area

src/pipeline.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicCI/CD & Pipelines

DifficultyHard

Est. time26 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace