Build stuck at createPagesStatefully

[Graham42]

Description

Build never finishes, gets stuck at createPagesStatefully

Environment

Gatsby version: 1.9.177
Node.js version: 8.9.4
Operating System: Ubuntu 16.04.3

File contents (if changed):

Nothing was changed.

Actual result

Build was stuck for 10 minutes until I killed it. Log:

success delete html files from previous builds — 0.040 s
success open and validate gatsby-config.js — 0.004 s
success copy gatsby files — 0.015 s
success onPreBootstrap — 0.005 s
success source and transform nodes — 0.014 s
success building schema — 0.068 s
success createLayouts — 0.023 s
success createPages — 0.000 s
⠐ createPagesStatefully^C

Expected behavior

Site should build.

Steps to reproduce

1. npm install -g gatsby

2. gatsby new gatsby-site && cd gatsby-site

3. gatsby build

[dannywils]

Same behavior on Windows 10 (node v8.9.4)

[tomazy]

Looks like this commit is the culprit: 6bbc0d1

[nsimonson]

Looks like it's because done is never called here on a production build: https://github.com/gatsbyjs/gatsby/blob/6bbc0d17a84a532c4d58ba5cba852be232114b51/packages/gatsby/src/internal-plugins/dev-404-page/gatsby-node.js

[monsieurnebo]

Same here, our deployment via CircleCI is stuck since gatsby v1.9.177.

#!/bin/bash -eo pipefail
npm run build:dist

> @foo/bar@1.0.3 build:dist /home/circleci/project
> ./scripts/dist.sh

Running Gatsby's Webpack
 - Env  : development
 - Path : 
 - URI  : https://dev.foobar.fr
success delete html files from previous builds — 0.054 s
success open and validate gatsby-config.js — 0.007 s
success copy gatsby files — 0.023 s
success onPreBootstrap — 0.007 s
success source and transform nodes — 0.024 s
success building schema — 0.129 s
success createLayouts — 0.009 s
success createPages — 0.001 s
Too long with no output (exceeded 10m0s)

🚨

[situplastik]

Same error. I think as @tomazy and @nsimonson that the problem is this commit: 6bbc0d1

[Graham42]

Would be good to have some integration tests to prevent something like this from happening in the future... should I open a separate issue for that?

[m-allanson]

@Graham42 There's plans for this but it's still a work in progress: #3242

[rdricco]

Same here on Gitlab CI.

[mpolinowski]

+1 Downgrading gatsby to v1.9.167 solved it for me. Thx m-allanson for the tip

[calcsam]

Fixed here: 7bb93fe

[Graham42]

Thanks all for the quick resolution.

[monsieurnebo]

Thanks!