This repository has been archived by the owner on Nov 10, 2022. It is now read-only.
Build failing #689
Comments
nzakas
added
bug
|
closed by #690 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like eslint.org hasn't successfully deployed in a couple of weeks. Here's the log:
Netlify Build Log
7:10:47 AM: Build ready to start 7:10:49 AM: build-image version: 9cade8af58c2cf3a17a1e9433d2e979149488837 7:10:49 AM: build-image tag: v3.3.5 7:10:49 AM: buildbot version: 036f37945d6de439a17a554b3ae02e2f8f0f1fb0 7:10:49 AM: Fetching cached dependencies 7:10:49 AM: Starting to download cache of 153.7MB 7:10:51 AM: Finished downloading cache in 2.268544724s 7:10:51 AM: Starting to extract cache 7:10:59 AM: Finished extracting cache in 7.101883019s 7:10:59 AM: Finished fetching cache in 9.584823588s 7:10:59 AM: Starting to prepare the repo for build 7:10:59 AM: Preparing Git Reference refs/heads/master 7:11:00 AM: Starting build script 7:11:00 AM: Installing dependencies 7:11:01 AM: Started restoring cached node version 7:11:05 AM: Finished restoring cached node version 7:11:06 AM: v12.14.1 is already installed. 7:11:07 AM: Now using node v12.14.1 (npm v6.13.4) 7:11:07 AM: Attempting ruby version 2.6.2, read from environment 7:11:09 AM: Using ruby version 2.6.2 7:11:09 AM: Using PHP version 5.6 7:11:09 AM: Started restoring cached node modules 7:11:09 AM: Finished restoring cached node modules 7:11:10 AM: Started restoring cached go cache 7:11:10 AM: Finished restoring cached go cache 7:11:10 AM: unset GOOS; 7:11:10 AM: unset GOARCH; 7:11:10 AM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64'; 7:11:10 AM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}"; 7:11:10 AM: go version >&2; 7:11:10 AM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env'; 7:11:10 AM: go version go1.12 linux/amd64 7:11:10 AM: Installing missing commands 7:11:10 AM: Verify run directory 7:11:10 AM: Executing user command: npm run build 7:11:11 AM: > eslint-website@1.0.0 build /opt/build/repo 7:11:11 AM: > npm run build:eleventy && npm run build:less && npm run build:webpack 7:11:11 AM: > eslint-website@1.0.0 build:eleventy /opt/build/repo 7:11:11 AM: > eleventy --quiet 7:11:56 AM: Copied 3 items / Wrote 3413 files in 44.08 seconds (12.9ms each, v0.10.0) 7:11:57 AM: > eslint-website@1.0.0 build:less /opt/build/repo 7:11:57 AM: > lessc src/styles/main.less _site/assets/styles/main.css --clean-css --source-map=_site/assets/styles/main.css.map 7:12:00 AM: > eslint-website@1.0.0 build:webpack /opt/build/repo 7:12:00 AM: > webpack --mode=production 7:12:12 AM: ERROR in ./src/js/demo/components/App.jsx 7:12:12 AM: Module not found: Error: Can't resolve '../node_modules/eslint/lib/linter/linter' in '/opt/build/repo/src/js/demo/components' 7:12:12 AM: @ ./src/js/demo/components/App.jsx 43:0-68 63:17-29 7:12:12 AM: @ ./src/js/demo/index.js 7:12:12 AM: ERROR in chunk demo [entry] 7:12:12 AM: demo.js 7:12:12 AM: /opt/build/repo/node_modules/babel-loader/lib/index.js??ref--4!/opt/build/repo/src/js/demo/index.js 8d9c08418e3c67681b9089441452bb1e 7:12:12 AM: Unexpected token (64:17) 7:12:12 AM: | }(); 7:12:12 AM: | 7:12:12 AM: | var linter = new !(function webpackMissingModule() { var e = new Error("Cannot find module '../node_modules/eslint/lib/linter/linter'"); e.code = 'MODULE_NOT_FOUND'; throw e; }()).Linter(); 7:12:12 AM: | var rules = linter.getRules(); 7:12:12 AM: | var ruleNames = Array.from(rules.keys()); 7:12:13 AM: npm 7:12:13 AM: ERR! code ELIFECYCLE 7:12:13 AM: npm 7:12:13 AM: ERR! 7:12:13 AM: errno 2 7:12:13 AM: npm 7:12:13 AM: ERR! eslint-website@1.0.0 build:webpack: `webpack --mode=production` 7:12:13 AM: npm 7:12:13 AM: ERR! Exit status 2 7:12:13 AM: npm 7:12:13 AM: ERR! 7:12:13 AM: npm ERR! 7:12:13 AM: Failed at the eslint-website@1.0.0 build:webpack script. 7:12:13 AM: npm 7:12:13 AM: ERR! This is probably not a problem with npm. There is likely additional logging output above. 7:12:13 AM: npm 7:12:13 AM: ERR! A complete log of this run can be found in: 7:12:13 AM: npm ERR! 7:12:13 AM: /opt/buildhome/.npm/_logs/2020-02-03T15_12_13_275Z-debug.log 7:12:13 AM: failed during stage 'building site': Build script returned non-zero exit code: 2 7:12:13 AM: npm 7:12:13 AM: ERR! 7:12:13 AM: code ELIFECYCLE 7:12:13 AM: npm 7:12:13 AM: ERR! errno 2 7:12:13 AM: Shutting down logging, 29 messages pendingThe text was updated successfully, but these errors were encountered: