Incident Dossier

The Pipeline Stage That Always Won

A CI runner executes each pipeline stage by handing the stage's script to a runner function. Stages that throw should be reported as failures so the upstream orchestrator can stop the build and surface the error. Instead, every stage — including the ones whose runners threw — is being reported as successful. The build never fails; what does it mean for a stage to 'succeed' when its runner raised?

Initial failing signalrunStage marks a stage whose runner throws as ok:trueExpected behavior: runStage({name:'lint',...}, throwingRunner).ok === false · actual behavior: runStage({name:'lint',...}, throwingRunner).ok === true

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Read runStage in src/pipeline.js.
Look at the catch branch — what does it promise about the result?
Make a runner that throws be reported as 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

DifficultyEasy

Est. time10 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