Comments (8)
@benbayard -- Holla! Can you get me a reproduction within this repo (against one of the /examples
tests) and with upgrade steps?
from rowdy.
@ryan-roemer let me try.
from rowdy.
Hey @ryan-roemer ! Yes, I can reproduce this with an example.
Changing scripts.test-webdriverio-per-test-client
to cd examples/mocha/webdriverio && mocha --require ./setup-per-test-client --use_strict
produces the same error above in the before all hook. Here is the output from npm-debug.log
:
0 info it worked if it ends with ok
1 verbose cli [ '/Users/ben/.nvm/versions/node/v5.11.0/bin/node',
1 verbose cli '/Users/ben/.nvm/versions/node/v5.11.0/bin/npm',
1 verbose cli 'run',
1 verbose cli 'test-webdriverio' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'pretest-webdriverio',
4 verbose run-script 'test-webdriverio',
4 verbose run-script 'posttest-webdriverio' ]
5 info lifecycle [email protected]~pretest-webdriverio: [email protected]
6 silly lifecycle [email protected]~pretest-webdriverio: no script for pretest-webdriverio, continuing
7 info lifecycle [email protected]~test-webdriverio: [email protected]
8 verbose lifecycle [email protected]~test-webdriverio: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~test-webdriverio: PATH: /Users/ben/.nvm/versions/node/v5.11.0/lib/node_modules/npm/bin/node-gyp-bin:/Users/ben/Projects/github.com/FormidibleLabs/rowdy/node_modules/.bin:/Users/ben/.nvm/versions/node/v5.11.0/bin:./node_modules/.bin:/Users/ben/.rbenv/shims:/Users/ben/.nvm/versions/node/v5.11.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
10 verbose lifecycle [email protected]~test-webdriverio: CWD: /Users/ben/Projects/github.com/FormidibleLabs/rowdy
11 silly lifecycle [email protected]~test-webdriverio: Args: [ '-c',
11 silly lifecycle 'npm run test-webdriverio-manual-config && npm run test-webdriverio-per-test-client' ]
12 silly lifecycle [email protected]~test-webdriverio: Returned: code: 1 signal: null
13 info lifecycle [email protected]~test-webdriverio: Failed to exec test-webdriverio script
14 verbose stack Error: [email protected] test-webdriverio: `npm run test-webdriverio-manual-config && npm run test-webdriverio-per-test-client`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/Users/ben/.nvm/versions/node/v5.11.0/lib/node_modules/npm/lib/utils/lifecycle.js:244:16)
14 verbose stack at emitTwo (events.js:100:13)
14 verbose stack at EventEmitter.emit (events.js:185:7)
14 verbose stack at ChildProcess.<anonymous> (/Users/ben/.nvm/versions/node/v5.11.0/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack at emitTwo (events.js:100:13)
14 verbose stack at ChildProcess.emit (events.js:185:7)
14 verbose stack at maybeClose (internal/child_process.js:850:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid [email protected]
16 verbose cwd /Users/ben/Projects/github.com/FormidibleLabs/rowdy
17 error Darwin 15.4.0
18 error argv "/Users/ben/.nvm/versions/node/v5.11.0/bin/node" "/Users/ben/.nvm/versions/node/v5.11.0/bin/npm" "run" "test-webdriverio"
19 error node v5.11.0
20 error npm v3.8.7
21 error code ELIFECYCLE
22 error [email protected] test-webdriverio: `npm run test-webdriverio-manual-config && npm run test-webdriverio-per-test-client`
22 error Exit status 1
23 error Failed at the [email protected] test-webdriverio script 'npm run test-webdriverio-manual-config && npm run test-webdriverio-per-test-client'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the rowdy package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error npm run test-webdriverio-manual-config && npm run test-webdriverio-per-test-client
23 error You can get information on how to open an issue for this project with:
23 error npm bugs rowdy
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls rowdy
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
from rowdy.
@benbayard -- It looks like the issue is that portscanner
requires an ancient version of [email protected]
that still has this (now closed) issue: caolan/async#189
UPDATE: portscanner
has a PR to update async which should fix this: baalexander/node-portscanner#37
Hopefully we can just wait on that and update portscanner...
from rowdy.
... but that PR is old and unmerged. If you can suggest a new lib / code snippet to detect if a server is listening already on a port, I can swap it out for portscanner
...
from rowdy.
Update: portscanner has updated async to 1.5.2. Released a new minor version 1.1.0.
from rowdy.
So, the portscanner thing is fixed on just a reinstall (picking up minor), but vargs
fails now:
$ npm run test-wd-default-config -- --use_strict
> [email protected] test-wd-default-config /Users/rye/scm/fmd/rowdy
> cd examples/mocha/wd && mocha "--use_strict"
/Users/rye/scm/fmd/rowdy/node_modules/vargs/lib/vargs.js:24
exports.Constructor = function Vargs(arguments) {
^^^^^^^^^
SyntaxError: Unexpected eval or arguments in strict mode
Oh, and for anyone watching along, you can repro this on the unchanged repo with:
$ npm run test-wd-default-config -- --use_strict
More info:
$ npm ls vargs
[email protected] /Users/rye/scm/fmd/rowdy
└─┬ [email protected]
└── [email protected]
from rowdy.
OK, so wd
has the offending vargs
, but that's an optional install. webdriverio
is the recommended engine (it's what I use) and those tests now work just fine and should for this app as a real dependency.
Closing!
@benbayard -- Let me know if anything else crops up!
from rowdy.
Related Issues (20)
- Win: Phantom not executable.
- Mocha Adapter: Don't start local selenium when using SL/BS HOT 1
- Make selenium-standalone optional dependency.
- Webdriver.io: Implement and refactor base client to more abstract.
- Config: Add matrix of _all_ SL/BS options
- Sauce Labs: Status missed for `perTest` and `refreshClient` HOT 3
- BrowserStack: Add guacamole integration
- Travis: Local selenium server start detection fails.
- BrowserStack: Add Travis retries.
- Document Configuration + Refactor
- BUG: SauceLabs + Safari Flake / Bug (?) HOT 8
- BUG: Figure out / re-enable browserstack. HOT 3
- Error: Bad ROWDY_SETTINGS path: sauceLabs.IE_11_Windows_2012_R2_Desktop HOT 9
- BUG: Can't override server.start. HOT 1
- Remove lodash dependency.
- Saucelabs DELETE /session occurs early on certain browsers. HOT 2
- How to apply wdio config? HOT 4
- rowdy does not handle selenium opts.basePath HOT 2
- CI: Hone down node.js to 8, 10, 11 and remove rest.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rowdy.