search

angular / benchpress-tree

A reference implementation of a benchpress deep-tree benchmark as seen in Angular
37 stars 14 forks source link

Testing error #10

Open oplummer-sysomos opened 9 years ago

oplummer-sysomos commented 9 years ago

After following the instructions and trying to run the provided protractor test, i get the following error:

Using ChromeDriver directly... [launcher] Running 1 instances of WebDriver [launcher] Error: SyntaxError: Unexpected token ) at goog.loadModuleFromSource_ (/Users/oplummer/Documents/projects/benchpress-guild2/benchpress-tree/node_modules/benchpress/node_modules/selenium-webdriver/lib/goog/base.js:1123:19) at Object.goog.loadModule (/Users/oplummer/Documents/projects/benchpress-guild2/benchpress-tree/node_modules/benchpress/node_modules/selenium-webdriver/lib/goog/base.js:1085:46) at /Users/oplummer/Documents/projects/benchpress-guild2/benchpress-tree/node_modules/benchpress/nodemodules/selenium-webdriver/lib/webdriver/promise.js:1:6 at Object.exports.runInContext (vm.js:44:17) at Object.Context.closure.goog.retrieveAndExecModule (/Users/oplummer/Documents/projects/benchpress-guild2/benchpress-tree/node_modules/benchpress/node_modules/selenium-webdriver/_base.js:135:8) at :1:6 at Object.exports.runInContext (vm.js:44:17) at Context.closure.closure.vm.createContext.CLOSURE_IMPORT_SCRIPT (/Users/oplummer/Documents/projects/benchpress-guild2/benchpress-tree/node_modules/benchpress/node_modules/selenium-webdriver/base.js:104:12) at Object.goog.importScript (/Users/oplummer/Documents/projects/benchpress-guild2/benchpress-tree/node_modules/benchpress/nodemodules/selenium-webdriver/lib/goog/base.js:879:9) at Object.goog.importModule (/Users/oplummer/Documents/projects/benchpress-guild2/benchpress-tree/node_modules/benchpress/node_modules/selenium-webdriver/lib/goog/base.js:900:14) [launcher] Process exited with error code 100

ghost commented 8 years ago

Same error for me. Apparently this is an issues in protractor/selenium itself. image

ghost commented 8 years ago

This can be easily fixed by upgrading node version >= V4.4.4