Abort trap: 6 #3
Comments
|
Hello, I just tried to reproduce your issue by pulling and starting the repository and was not able to. Do you have gulp installed globally on your machine?
|
|
Hi Ethan, (matchminer-ui) ~/matchminer-ui$ $ npm install -g gulp
then: (matchminer-ui) ~/matchminer-ui$ gulp test |
|
Hmmm I'm not sure if being in a conda environment effects any of the gulp processes. Could you try running the commands outside the environment and see if there is any difference? |
|
Tried just in bash with no conda env. Identical error. |
|
Also: tried to build a docker container (there is Dockerfile in the repo even though the docs do not mention dockerization). the build arrived almost to the end and the exited with this really long error trace (I had to cut out the middle section of it due to the comment length limit of 65K chars) ending with "The command '/bin/sh -c gulp test' returned a non-zero code: 1", so it might be the same issue: [16:14:35] Starting 'test'... PhantomJS 2.1.1 (Linux 0.0.0) Matches Service Unit Tests Public methods should be able to get the match counts FAILED |
|
what version of node/npm are you using? on my machine I have node 9.10.1 and npm 5.6.0 also from the logs you posted it looks like all the tests are failing. just as a test, if you comment out line 22 in the dockerfile |
|
my node version is v8.12.0
my npm version is 6.4.1
OS: tried both El Capitan 10.11.6 and High Sierra 10.13.6
…On Tue, Oct 16, 2018 at 4:54 PM Ethan ***@***.***> wrote:
what version of node/npm are you using? on my machine I have node 9.10.1
and npm 5.6.0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC7jzEw7OSs4jsmAUrCSMcsMKbDG6k2gks5ulfMLgaJpZM4XZorl>
.
|
|
I commented out line 22 in the dockerfile Basically, there is the same failure from |
|
Ah, I meant after you comment out As far as gulp goes, I'm not entirely sure why your version is so unhappy. When I run |
|
With npm WARN jit-grunt@0.9.1 requires a peer of grunt@~0.4.0 but none was installed. However, |
|
As of |
|
I see. to start the container you need to run |
|
Tried It ends with: Then I check Just for curiosity checked aforementioned directory (STEP 10): So what is the way to access the newly build container? |
|
Looks like I got image successfully build (with But an atempt to start the container results in this error (both by REPOSITORY and IMAGE ID): |
|
alright glad the container is up! So I think the reason the container is not starting is because you are trying to run |
|
Sorry I am lost. The container is not up. Only the image is created. I did not get the comment about |
|
ah I see. sorry about that. so there are a few things going on let me try to explain as best I can. Earlier I was talking about adding a CMD command to the docker file to execute once the container is started. To do that you can go to the dockerfile and add If it is not crucial to dockerize the UI at this time, I would suggest trying to get the app up and running with the API and db outside of containers first, and then coming back to containerize them afterwards since that will probably be easier |
|
Thanks. OK, I tried adding After docker build, when I run Adding grunt's full path to Dockerfile CMD line ( As of not dockerized way - when I run gulp build, I get that Abort trap 6 th started this thread. Running $ gulp serve from my project directory gives this: I wonder if all these problems happen to me because I am on MAc or maybe because I am on specific Mac OS (El Capitan)? Are you on Ubuntu ? |
|
Hi Ethan, Today I tried to docker build again but on Mac OSX 10.13.6 ( High Sierra ) and the behaviour is different. Now: Again, all good! (but It does not go back to the command line prompt, just hangs there. |
|
Some update: the error about "Abort trap 6" goes away if I run this : |
Mac Os X El Capitan 10.11.6
conda 4.5.11
In a conda environment:
Manual build: after cloning and installing npm, bower, gulp, npm audit fix, etc I arrived to the steps
gulp testandgulp serveBoth gave me the same error:
The text was updated successfully, but these errors were encountered: