errors while using ibazel about angular-bazel-example HOT 6 CLOSED

First, you can repro it with just bazel, so it's not related to watch mode.
The root cause here is the npm_install failed: ... signal 6) but it doesn't give info on why that failed.

Can you run again with --subcommands --verbose_failures ?

from angular-bazel-example.

donno if its right command with bazel but here is output

from angular-bazel-example.

Ouch, you do have the command-line correct but it looks like this failure is during an earlier phase of execution when those flags don't do anything (they relate to running actions, but you never get that far because the actions require an npm_install as input and this fails.
Closest I can find in a google search is that maybe there's some native compilation going on in one of those modules being installed.
Let's see if I can get enough info to repro... can you give your OS version, bazel info release, anything interesting about your network/proxy setup, anything interesting about your libc or other bits of C++ toolchain on this machine?
Another thing to try is cd $(bazel info output_base)/external/build_bazel_rules_typescript/internal/devserver and run npm install there, should have the same problem but maybe it will give more debug output

from angular-bazel-example.

Network : Wired Connected - 1000 Mb/s , no proxy

After runing npm install from cd $(bazel info ...ernal/devserver I get

GCC:

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.2.0-8ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) 

Hope it's enough.. thanks @alexeagle

from angular-bazel-example.

Hmm, I don't see any more clues from that output, it still dies with signal 6 and no clue why.
@gregmagolan is looking at changing the npm_install rule right now, let's debug this more after that lands, just in case we manage to fix it by accident.

from angular-bazel-example.

Let's continue at bazelbuild/rules_nodejs#101 where we track more closely

from angular-bazel-example.