netlify / netlify-statuskit

Netlify StatusKit is a template to deploy your own Status pages on Netlify.
https://www.netlify.com/status-pages/
MIT License
238 stars 41 forks source link

Deploy failed #57

Closed iLek2428 closed 5 years ago

iLek2428 commented 5 years ago
4:45:09 PM: Build ready to start
4:45:11 PM: build-image version: 9e0f207a27642d0115b1ca97cd5e8cebbe492f63
4:45:11 PM: build-image tag: v3.3.2
4:45:11 PM: buildbot version: 75cd99f62ada9e21edea53208e8baf0eab85a045
4:45:11 PM: Fetching cached dependencies
4:45:11 PM: Failed to fetch cache, continuing with build
4:45:11 PM: Starting to prepare the repo for build
4:45:12 PM: No cached dependencies found. Cloning fresh repo
4:45:12 PM: git clone https://github.com/netlify/netlify-statuskit
4:45:15 PM: Preparing Git Reference refs/heads/master
4:45:15 PM: Found netlify.toml. Overriding site configuration
4:45:15 PM: Starting build script
4:45:15 PM: Installing dependencies
4:45:17 PM: v10.15.3 is already installed.
4:45:18 PM: Now using node v10.15.3 (npm v6.4.1)
4:45:18 PM: Attempting ruby version 2.6.2, read from environment
4:45:19 PM: Using ruby version 2.6.2
4:45:20 PM: Using PHP version 5.6
4:45:20 PM: Started restoring cached node modules
4:45:20 PM: Finished restoring cached node modules
4:45:20 PM: Started restoring cached yarn cache
4:45:20 PM: Finished restoring cached yarn cache
4:45:20 PM: Installing yarn at version 1.13.0
4:45:20 PM: Installing Yarn!
4:45:20 PM: > Downloading tarball...
4:45:20 PM: [1/2]: https://yarnpkg.com/downloads/1.13.0/yarn-v1.1
4:45:20 PM: 3.0.tar.gz --> /tmp/yarn.tar.gz.BMbcDhm7gs
4:45:20 PM:   % Total    % Received % Xferd  Average Speed   Tim
4:45:20 PM: e    Time     Time  Current
4:45:20 PM:                                  Dload  Upload   Total   Spent    Left  Speed
4:45:20 PM: 
  0     0    0
4:45:20 PM:    0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
4:45:20 PM: 
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:
4:45:20 PM: --     0
4:45:20 PM: 
100    93  100    93    0     0    329      0 --:--:-- --:--:-- --:--:--   328
4:45:21 PM: 
100   609    0   609    0     0    894      0 --:--:-- --:--:--
4:45:21 PM:  --:--:--   894
4:45:21 PM: 
100 1142k  100 1142k    0     0  1051k      0  0:00:01
4:45:21 PM:  0:00:01 --:--:-- 1051k
4:45:21 PM: [2/2]: https://yarnpkg.com/downloads/1.
4:45:21 PM: 13.0/yarn-v1.13.0.tar.gz.asc --> /tmp/yarn.tar.gz.BMbcDhm7gs.asc
4:45:21 PM: 
100    97  100    97    0     0   2123      0 --:--:-- --:--:-- --:--:--
4:45:21 PM: 2123
4:45:21 PM: 
  0     0    0     0    0     0      0      0 --:--:-
4:45:21 PM: - --:--:-- --:--:--     0
100   613    0   613    0     0   3709      0
4:45:21 PM:  --:--:-- --:--:-- --:--:--  598k
4:45:21 PM: 
100   832  100   832    0     0   4026      0 --:--:-- -
4:45:21 PM: -:--:-- --:--:--  4026
4:45:21 PM: > Verifying integrity...
4:45:21 PM: gpg: Signature made Tue 18 Dec 2018 04:04:55 PM UTC using RSA key ID B6FF4DE3
4:45:21 PM: gpg: Good signature from "Yarn Packaging <yarn@dan.cx>"
4:45:21 PM: gpg: Note: This key has expired!
4:45:21 PM: Primary key fingerprint: 72EC F46A 56B4 AD39 C907  BBB7 1646 B01B 86E5 0310
4:45:21 PM:      Subkey fingerprint: E219 30C4 D0A4 AA46 1858  1F7A E074 D16E B6FF 4DE3
4:45:21 PM: > GPG signature looks good
4:45:21 PM: > Extracting to ~/.yarn...
4:45:21 PM: > Adding to $PATH...
4:45:21 PM: > We've added the following to your /opt/buildhome/.profile
4:45:21 PM: > If this isn't the profile of your current shell then please add the following to your correct profile:
4:45:21 PM: export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
4:45:21 PM: 
4:45:22 PM: > Successfully installed Yarn 1.13.0! Please open another terminal where the `yarn` command will now be available.
4:45:22 PM: Installing NPM modules using Yarn version 1.13.0
4:45:23 PM: yarn install v1.13.0
4:45:23 PM: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
4:45:23 PM: [1/4] Resolving packages...
4:45:24 PM: [2/4] Fetching packages...
4:45:36 PM: info fsevents@1.0.17: The platform "linux" is incompatible with this module.
4:45:36 PM: info "fsevents@1.0.17" is an optional dependency and failed compatibility check. Excluding it from installation.
4:45:36 PM: [3/4] Linking dependencies...
4:45:36 PM: warning " > babel-loader@6.2.10" has unmet peer dependency "babel-core@^6.0.0".
4:45:40 PM: [4/4] Building fresh packages...
4:45:40 PM: success Saved lockfile.
4:45:40 PM: Done in 17.40s.
4:45:40 PM: NPM modules installed using Yarn
4:45:41 PM: Started restoring cached go cache
4:45:41 PM: Finished restoring cached go cache
4:45:41 PM: unset GOOS;
4:45:41 PM: unset GOARCH;
4:45:41 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
4:45:41 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
4:45:41 PM: go version >&2;
4:45:41 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
4:45:41 PM: go version go1.12 linux/amd64
4:45:41 PM: Installing missing commands
4:45:41 PM: Verify run directory
4:45:41 PM: Executing user command: npm run build
4:45:41 PM: > netlify-statusKit@1.0.0 build /opt/build/repo
4:45:41 PM: > gulp build
4:45:42 PM: [09:45:42]
4:45:42 PM: Requiring external module babel-register
4:45:42 PM: gulp[1306]: ../src/node_contextify.cc:626:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsString()' failed.
4:45:42 PM:  1: 0x8dc510 node::Abort() [gulp]
4:45:42 PM:  2: 0x8dc5e5  [gulp]
4:45:42 PM:  3: 0x91081e node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [gulp]
4:45:42 PM:  4: 0xb6166b  [gulp]
4:45:42 PM:  5: 0xb63602 v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [gulp]
4:45:42 PM:  6: 0x364db845be1d
4:45:42 PM: Aborted (core dumped)
4:45:42 PM: npm
4:45:42 PM:  ERR! code ELIFECYCLE
4:45:44 PM: failed during stage 'building site': Build script returned non-zero exit code: 134
4:45:42 PM: npm
4:45:45 PM: Shutting down logging, 33 messages pending
steveoh commented 5 years ago

What does your netlify build command look like?

mabreyes commented 5 years ago

Same error. Similar to @iLek2428 we created a status page via this site https://www.netlify.com/status-pages/. Added information such as site title, logo, etc. After providing this information, I was then redirected to the production deploy page. After few moments, there came the error. If you're asking what the build command is, I could not tell as it was not prompted on the process of creating the status page. Also checked the repository supposedly created in the process, it is blank.

steveoh commented 5 years ago

We don't own the netlify on boarding process any longer but it sounds like something is missing. I know some new build images were added and I think some things that were magic before are now required. Maybe I'll try the status-pages walkthrough and see if I can figure out what is missing.

steveoh commented 5 years ago

I just tried the netlify status pages deploy twice and it did not push any files into the new repository so the build failed.

@marcreyesph is that what you also noticed?

@fool or anyone at netlify know or care that that is broken?

steveoh commented 5 years ago

I made this repo a template and pushed a build and it also failed.

steveoh commented 5 years ago

It has to do with the new base image. https://www.netlify.com/blog/2019/03/14/a-more-flexible-build-architecture-with-updated-linux/

Ubuntu Trusty 14.04
Legacy build image for older sites

Ubuntu Xenial 16.04 (default)
Current default build image for all new sites

I assume some dependency is missing for the xenial image.

steveoh commented 5 years ago

I updated the deps and a few other things and the builds are now working. You'll need to use this template or pull the changes into your fork.

Please comment if this is still an issue and I'll reopen.

merveillevaneck commented 4 years ago

this is still an issue

steveoh commented 4 years ago

@merveillevaneck do you have more information to back your statement?