11:59:03 AM: Build ready to start
11:59:04 AM: build-image version: 9e0f207a27642d0115b1ca97cd5e8cebbe492f63
11:59:04 AM: build-image tag: v3.3.2
11:59:04 AM: buildbot version: ef8d0929ed0baabafd8bbb7d0b021e1fc24180c0
11:59:05 AM: Fetching cached dependencies
11:59:05 AM: Starting to download cache of 124.7MB
11:59:06 AM: Finished downloading cache in 1.04022469s
11:59:06 AM: Starting to extract cache
11:59:11 AM: Finished extracting cache in 5.567677404s
11:59:11 AM: Finished fetching cache in 6.676466977s
11:59:11 AM: Starting to prepare the repo for build
11:59:12 AM: Preparing Git Reference pull/89/head
11:59:12 AM: Found netlify.toml. Overriding site configuration
11:59:12 AM: Different publish path detected, going to use the one specified in the toml file: 'web/public' versus '' in the site
11:59:12 AM: Different build command detected, going to use the one specified in the toml file: 'npm install && npm run build' versus '' in the site
11:59:12 AM: Different base path detected, going to use the one specified in the toml file: 'web' versus '' in the site
11:59:12 AM: Starting build script
11:59:13 AM: Installing dependencies
11:59:13 AM: Started restoring cached node version
11:59:15 AM: Finished restoring cached node version
11:59:16 AM: v10.16.0 is already installed.
11:59:19 AM: Now using node v10.16.0 (npm v6.9.0)
11:59:20 AM: Attempting ruby version 2.6.2, read from environment
11:59:21 AM: Using ruby version 2.6.2
11:59:21 AM: Using PHP version 5.6
11:59:21 AM: Started restoring cached node modules
11:59:21 AM: Finished restoring cached node modules
11:59:21 AM: Started restoring cached go cache
11:59:21 AM: Finished restoring cached go cache
11:59:21 AM: unset GOOS;
11:59:21 AM: unset GOARCH;
11:59:21 AM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
11:59:21 AM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
11:59:21 AM: go version >&2;
11:59:21 AM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
11:59:21 AM: go version go1.12 linux/amd64
11:59:21 AM: Installing missing commands
11:59:21 AM: Verify run directory
11:59:21 AM: Executing user command: npm install && npm run build
11:59:31 AM: npm
11:59:31 AM: WARN [email protected] requires a peer of typescript@* but none is installed. You must install peer dependencies yourself.
11:59:31 AM: npm
11:59:31 AM: WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
11:59:31 AM: npm WARN
11:59:31 AM: notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
11:59:31 AM: audited 21707 packages in 8.774s
11:59:31 AM: found 0 vulnerabilities
11:59:31 AM: > [email protected] build /opt/build/repo/web
11:59:31 AM: > gatsby build
11:59:33 AM: success open and validate gatsby-configs — 0.033
11:59:34 AM: success load plugins — 0.130
11:59:34 AM: success onPreInit — 0.022
11:59:34 AM: success delete html and css files from previous builds — 0.025
11:59:34 AM: success initialize cache — 0.023
11:59:34 AM: success copy gatsby files — 0.048
11:59:34 AM: success onPreBootstrap — 0.031
11:59:34 AM: success source and transform nodes — 0.061
11:59:34 AM: error ENOSPC: System limit for number of file watchers reached, watch '/opt/build/repo/web/gatsby-config.js'
11:59:34 AM: UNHANDLED EXCEPTION ENOSPC: System limit for number of file watchers reached, watch '/opt/build/repo/web/gatsby-config.js'
11:59:34 AM: See our docs page for more info on this error: https://gatsby.dev/issue-how-to
11:59:34 AM:
11:59:34 AM: Error: ENOSPC: System limit for number of file watchers reached, watch '/opt/b uild/repo/web/gatsby-config.js'
11:59:34 AM:
11:59:34 AM: - watchers.js:165 FSWatcher.start
11:59:34 AM: internal/fs/watchers.js:165:26
11:59:34 AM:
11:59:34 AM: - nodefs-handler.js:38 createFsWatchInstance
11:59:34 AM: [web]/[chokidar]/lib/nodefs-handler.js:38:15
11:59:34 AM:
11:59:34 AM: - nodefs-handler.js:81 setFsWatchListener
11:59:34 AM: [web]/[chokidar]/lib/nodefs-handler.js:81:15
11:59:34 AM:
11:59:34 AM: - nodefs-handler.js:233 FSWatcher.NodeFsHandler._watchWithNodeFs
11:59:34 AM: [web]/[chokidar]/lib/nodefs-handler.js:233:14
11:59:34 AM:
11:59:34 AM: - nodefs-handler.js:262 FSWatcher.NodeFsHandler._handleFile
11:59:34 AM: [web]/[chokidar]/lib/nodefs-handler.js:262:21
11:59:34 AM:
11:59:34 AM: - nodefs-handler.js:495 FSWatcher.<anonymous>
11:59:34 AM: [web]/[chokidar]/lib/nodefs-handler.js:495:21
11:59:34 AM: failed during stage 'building site': Build script returned non-zero exit code: 1
11:59:34 AM:
11:59:34 AM:
11:59:34 AM: npm
11:59:34 AM: ERR! code
11:59:34 AM: ELIFECYCLE
11:59:34 AM: npm ERR! errno 1
11:59:34 AM: npm
11:59:34 AM: ERR! [email protected] build: `gatsby build`
11:59:34 AM: npm ERR! Exit status 1
11:59:34 AM: npm ERR!
11:59:34 AM: npm ERR! Failed at the [email protected] build script.
11:59:34 AM: npm ERR!
11:59:34 AM: This is probably not a problem with npm. There is likely additional logging output above.
11:59:34 AM: npm
11:59:34 AM: ERR! A complete log of this run can be found in:
11:59:34 AM: npm ERR! /opt/buildhome/.npm/_logs/2019-07-19T09_59_34_506Z-debug.log
11:59:34 AM: Skipping functions preparation step: no functions directory set
11:59:34 AM: Caching artifacts
11:59:34 AM: Started saving node modules
11:59:34 AM: Finished saving node modules
11:59:34 AM: Started saving pip cache
11:59:34 AM: Finished saving pip cache
11:59:34 AM: Started saving emacs cask dependencies
11:59:34 AM: Finished saving emacs cask dependencies
11:59:34 AM: Started saving maven dependencies
11:59:34 AM: Finished saving maven dependencies
11:59:34 AM: Started saving boot dependencies
11:59:34 AM: Finished saving boot dependencies
11:59:34 AM: Started saving go dependencies
11:59:34 AM: Finished saving go dependencies
11:59:34 AM: Error running command: Build script returned non-zero exit code: 1
11:59:34 AM: Failing build: Failed to build site
11:59:34 AM: Finished processing build request in 29.956238231s