Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac OS: Abort trap 6 error when spawning script from within Node #6975

Closed
JeffML opened this issue May 25, 2016 · 2 comments
Closed

Mac OS: Abort trap 6 error when spawning script from within Node #6975

JeffML opened this issue May 25, 2016 · 2 comments
Labels
child_process Issues and PRs related to the child_process subsystem. macos Issues and PRs related to the macOS platform / OSX.

Comments

@JeffML
Copy link

JeffML commented May 25, 2016

Seeing the following errors:

./runTests.sh: line 14: 39479 Abort trap: 6           jasmine-node $f --junitreport --config server $1 --output "reports/${output}"
./runTests.sh: line 14: 39483 Abort trap: 6           jasmine-node $f --junitreport --config server $1 --output "reports/${output}"
./runTests.sh: line 14: 39484 Abort trap: 6           jasmine-node $f --junitreport --config server $1 --output "reports/${output}"
./runTests.sh: line 14: 39485 Abort trap: 6           jasmine-node $f --junitreport --config server $1 --output "reports/${output}"
./runTests.sh: line 14: 39486 Abort trap: 6           jasmine-node $f --junitreport --config server $1 --output "reports/${output}"

The culprit line in my node js app seems to be:

   var test = spawn("./runTests.sh", [url, server.nick], {
        cwd : frisbyRoot,
        stdio : [0, fs.openSync(outfile, "a"), //stdio
        fs.openSync(outfile, "a") //stderr
        ]
    });

The script itself is:

#!/bin/bash

if [[ $# -ne 2 ]]; then
  echo "Usage: $0 URL NICKNAME" >&2
  exit 1
fi

#FILES=./*_spec.js

FILES=`find . -name "*_spec.js"`

output=$2

for f in $FILES
do
jasmine-node $f --junitreport --config server $1 --output "reports/${output}"
done

version info:
Jeffs-WebTesting-MacBook-Pro:tests test$ npm ls -depth=0
tests@1.0.0 /Users/test/unit-tests/frisby/tests
├── frisby@0.8.5
├── jasmine@2.4.1
├── lodash@4.13.1
└── xml2js@0.4.16

Jeffs-WebTesting-MacBook-Pro:tests test$ npm -g ls -depth=0
/opt/local/lib
├── jasmine-node@1.14.5
├── junit-viewer@3.2.0
└── npm@2.15.3

node version: 4.4.3

OS X version: 10.10.5 (Yosemite)

Verified that I can run the jasmine tests from the command line via runTests.sh without error.

@bnoordhuis
Copy link
Member

Do you have a standalone test case for us to try? #6563 might be related, maybe you can try the patch from #6563 (comment)?

@bnoordhuis bnoordhuis added macos Issues and PRs related to the macOS platform / OSX. unconfirmed labels May 25, 2016
@mscdex mscdex added the child_process Issues and PRs related to the child_process subsystem. label May 25, 2016
@JeffML
Copy link
Author

JeffML commented May 26, 2016

This seems to be fixed with v6.2.0 installed. Thanks.

@JeffML JeffML closed this as completed May 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
child_process Issues and PRs related to the child_process subsystem. macos Issues and PRs related to the macOS platform / OSX.
Projects
None yet
Development

No branches or pull requests

3 participants