ng e2e fails with Error code 135 #2176

jtsom · 2016-09-16T16:50:49Z

Please provide us with the following information:

OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Mac OSX El Cap

Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.14
node: 6.6.0
os: darwin x64

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.

new application, start the server with ng serve and in another terminal window try to run the tests with ng e2e

The log given by the failure. Normally this include a stack trace and some
more information.


> a2test@0.0.0 pree2e /Users/John/Dev/Javascript/Angular/a2test
> webdriver-manager update

[12:50:02] I/update - chromedriver: file exists /Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.22mac32.zip
[12:50:02] I/update - chromedriver: unzipping chromedriver_2.22mac32.zip
[12:50:02] I/update - chromedriver: setting permissions to 0755 for /Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.22
[12:50:02] I/update - chromedriver: v2.22 up to date
[12:50:02] I/update - selenium standalone: file exists /Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar
[12:50:02] I/update - selenium standalone: v2.53.1 up to date

> a2test@0.0.0 e2e /Users/John/Dev/Javascript/Angular/a2test
> protractor "./protractor.conf.js"

[12:50:03] I/direct - Using ChromeDriver directly...
[12:50:03] I/launcher - Running 1 instances of WebDriver
[12:50:04] E/launcher - Error code: 135
[12:50:04] E/launcher - Error message: ECONNREFUSED connect ECONNREFUSED 127.0.0.1:53256
[12:50:04] E/launcher - Error: ECONNREFUSED connect ECONNREFUSED 127.0.0.1:53256
    at ClientRequest.<anonymous> (/Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/node_modules/selenium-webdriver/http/index.js:381:15)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:188:7)
    at Socket.socketErrorListener (_http_client.js:308:9)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at emitErrorNT (net.js:1271:8)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
From: Task: WebDriver.createSession()
    at Function.createSession (/Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:329:24)
    at Driver (/Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:778:38)
    at Direct.getNewDriver (/Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/built/driverProviders/direct.js:68:26)
    at Runner.createBrowser (/Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/built/runner.js:190:43)
    at /Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/built/runner.js:264:30
    at _fulfilled (/Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:796:13)
    at /Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:556:49
    at runSingle (/Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:137:13)
[12:50:04] E/launcher - Process exited with error code 135


npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/Cellar/node/6.6.0/bin/node" "/usr/local/bin/npm" "run" "e2e" "--" "./protractor.conf.js"
npm ERR! node v6.6.0
npm ERR! npm  v3.10.7
npm ERR! code ELIFECYCLE
npm ERR! a2test@0.0.0 e2e: `protractor "./protractor.conf.js"`
npm ERR! Exit status 135
npm ERR!
npm ERR! Failed at the a2test@0.0.0 e2e script 'protractor "./protractor.conf.js"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the a2test package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     protractor "./protractor.conf.js"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs a2test
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls a2test
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/John/Dev/Javascript/Angular/a2test/npm-debug.log

Some end-to-end tests failed, see above.

The text was updated successfully, but these errors were encountered:

amellnik · 2016-09-20T20:54:40Z

Are you behind a proxy by any chance?

filipesilva · 2016-10-03T12:47:34Z

You seem to have some hosts/ports blocked.

[12:50:04] E/launcher - Error message: ECONNREFUSED connect ECONNREFUSED 127.0.0.1:53256
[12:50:04] E/launcher - Error: ECONNREFUSED connect ECONNREFUSED 127.0.0.1:53256

There might be a way around it, but I'd advice to check https://github.com/angular/protractor on how to do it. The CLI just uses protractor for e2e tests.

jtsom · 2016-10-03T12:53:51Z

No, no proxy. And you do realize that 127.0.0.1 is the localhost, right? So no, there aren't any ports blocked.

ecozoic · 2016-10-12T22:45:52Z

I'm also getting this issue on my home PC (work computer works fine).

ecozoic · 2016-10-13T12:14:21Z

For me this turned out to be an issue w/ the latest version of Chrome (v54) and how it interacts w/ Chromedriver.

So when you install the latest Chromedriver via webdriver-manager update, right now it's installing the default Chromedriver version which is 2.22. In Chrome 54 they changed something w/ the Devtools API which breaks that version. I got around this issue by forcing webdriver-manager to download Chromedriver v.2.2.4 doing this:

webdriver-manager update --versions.chrome=2.24

That will download version v.2.24. However, if you are connecting to Protractor using directConnect: true in the config (which you probably are), protractor will still attempt to use the default (v.2.22) driver when running tests. To fix that, you need to specify a chromeDriver setting in protractor.conf.js as well. To get it to work on Windows and Unix platforms you can do something like this:

chromeDriver: `./node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.24${process.platform.indexOf('win') === 0 ? '.exe' : ''}`

Kind of annoying but at least it's working.

alexpopdev · 2016-10-13T13:53:59Z

Thanks @ecozoic your solution has helped running protractor tests again for Chrome 54.

jtsom · 2016-10-13T13:58:56Z

Just tried this on Mac OS Sierra and got a bunch of errors, on a pretty much stock Angular-CLI app:

> a2test@0.0.0 pree2e /Users/John/Dev/Javascript/Angular/a2test
> webdriver-manager update --versions.chrome=2.24

[09:56:22] I/downloader - chromedriver: downloading version 2.24
[09:56:22] I/downloader - curl -o /Users/John/Dev/Javascript/Angular/a2test/node_modules/webdriver-manager/selenium/chromedriver_2.24mac32.zip https://chromedriver.storage.googleapis.com/2.24/chromedriver_mac32.zip
[09:56:22] E/downloader - Error: Got code 404 from https://chromedriver.storage.googleapis.com/2.24/chromedriver_mac32.zip
[09:56:22] I/update - selenium standalone: file exists /Users/John/Dev/Javascript/Angular/a2test/node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar
[09:56:22] I/update - selenium standalone: v2.53.1 up to date
[09:56:22] E/downloader - Error: Got error Error: ENOENT: no such file or directory, stat '/Users/John/Dev/Javascript/Angular/a2test/node_modules/webdriver-manager/selenium/chromedriver_2.24mac32.zip' from https://chromedriver.storage.googleapis.com/2.24/chromedriver_mac32.zip

> a2test@0.0.0 e2e /Users/John/Dev/Javascript/Angular/a2test
> protractor "./protractor.conf.js"

[09:56:22] I/direct - Using ChromeDriver directly...
[09:56:22] I/launcher - Running 1 instances of WebDriver
[09:56:23] E/direct - Error code: 135
[09:56:23] E/direct - Error message: Could not find chromedriver at /Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.24
[09:56:23] E/direct - Error: Could not find chromedriver at /Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.24
    at Direct.getNewDriver (/Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/built/driverProviders/direct.js:65:27)
    at Runner.createBrowser (/Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/built/runner.js:198:43)
    at /Users/John/Dev/Javascript/Angular/a2test/node_modules/protractor/built/runner.js:277:30
    at _fulfilled (/Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:796:13)
    at /Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:556:49
    at runSingle (/Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:137:13)
    at flush (/Users/John/Dev/Javascript/Angular/a2test/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
[09:56:23] E/launcher - Process exited with error code 135


npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/Cellar/node/6.8.0/bin/node" "/usr/local/bin/npm" "run" "e2e" "--" "./protractor.conf.js"
npm ERR! node v6.8.0
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! a2test@0.0.0 e2e: `protractor "./protractor.conf.js"`
npm ERR! Exit status 135
npm ERR!
npm ERR! Failed at the a2test@0.0.0 e2e script 'protractor "./protractor.conf.js"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the a2test package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     protractor "./protractor.conf.js"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs a2test
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls a2test
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/John/Dev/Javascript/Angular/a2test/npm-debug.log

Some end-to-end tests failed, see above.

ecozoic · 2016-10-13T14:01:16Z

Yeah you might have to adjust the path of chromeDriver based on where it's actually installed. I have a Macbook at home but I haven't tested it on that one yet, still running on Windows 10 at the moment.

jtsom · 2016-10-13T14:35:21Z

Hm. Seems there isn't a "chromedriver" anywhere. I did a find . -name "*chromedriver*" in my node_modules folder and nothing came up.

nestoru · 2016-10-13T20:12:52Z

Thanks ecozoic for the workaround. Just sharing that in my case all I had to do was the below in order to solve our issue with protractor:

cd protractor/node_modules/webdriver-manager/bin
./webdriver-manager update --versions.chrome 2.24

jtsom · 2016-10-14T14:32:43Z

In my project (again, a simple Angular-cli app), there isn't anything under the node_modules/protractor/node_modules folder - it's empty.

I did find node_modules/protractor/bin/webdriver-manager, and when trying the command given, I get:

➜  bin git:(master) ✗ ./webdriver-manager update --versions.chrome 2.24
[10:28:21] I/file_manager - creating folder /Users/John/Dev/Javascript/Angular/a2test/node_modules/webdriver-manager/selenium
[10:28:21] I/downloader - selenium standalone: downloading version 2.53.1
[10:28:21] I/downloader - curl -o /Users/John/Dev/Javascript/Angular/a2test/node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar https://selenium-release.storage.googleapis.com/2.53/selenium-server-standalone-2.53.1.jar
[10:28:21] I/downloader - chromedriver: downloading version 2.24
[10:28:21] I/downloader - curl -o /Users/John/Dev/Javascript/Angular/a2test/node_modules/webdriver-manager/selenium/chromedriver_2.24mac32.zip https://chromedriver.storage.googleapis.com/2.24/chromedriver_mac32.zip
[10:28:22] E/downloader - Error: Got code 404 from https://chromedriver.storage.googleapis.com/2.24/chromedriver_mac32.zip
[10:28:22] E/downloader - Error: Got error Error: ENOENT: no such file or directory, stat '/Users/John/Dev/Javascript/Angular/a2test/node_modules/webdriver-manager/selenium/chromedriver_2.24mac32.zip' from https://chromedriver.storage.googleapis.com/2.24/chromedriver_mac32.zip

It looks like it's trying and failing to download chromedriver_2.24mac32.zip, which doesn't exist.

galicians · 2016-10-21T14:45:31Z

Exactly same error than jtsom.

mantisbayne · 2016-10-24T23:45:51Z

I am having this exact same problem since Chrome updated to v54 and getting the same errors when trying to download chromedriver version 2.24. Has anyone found a solution?

IcodeNet · 2016-10-26T08:44:31Z

If that helps anyone I manualy downloaded the chrome-driver version 2.24. from http://chromedriver.storage.googleapis.com/index.html
then dropped it in
C:\Users%UserProfile%\AppData\Local\Temp\chromedriver

and that did the job for me as when I run the commands now it finds it from the temp directory

kevin-ashton · 2016-10-26T16:19:52Z

@mantisbayne if you are still having problems you might try:

Make sure you are on protractor version 4.0.9 or higher in your project.
webdriver-manager is a dependency of protractor and has a config file specifying the driver version. You should be on 10.2.5 or above. Provided you are above that version it should automatically get the 2.24 driver. I was running into this problem on my CI and had to reset my dependency cache.

Providing you are on an updated version of protractor this problem should resolve itself automatically without manually downloading the chromedriver. I would nuke your node_modules directory and do a fresh npm install.

mantisbayne · 2016-10-26T16:29:24Z

I forgot I had posted on this thread too. I got a response from protractor that webdriver-manager was updated two days ago, so everything started working again once I updated to 4.0.9. & did npm install. Issue fixed

riddla · 2016-11-08T13:03:20Z

I'm still encountering this issue with the following (up to date) dependencies:

protractor version 4.0.9
webdriver-manager version 10.2.7
chromedriver version 2.25.426935
chrome version 54.0.2840.87

For the time being I switched to using Canary with the following settings within protractor.conf.js:

capabilities: {
  "browserName": "chrome",
"chromeOptions": {
    "binary": "/Users/XXX/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary"
  }
},

riddla · 2016-11-11T07:45:34Z

angular/protractor#1198 (comment) mentions a chromedriver bug and a temporary solution by setting export LANG=en_US.UTF-8.

export LANG=en_US.UTF-8
ng  e2e

... works for me.

…/issues/2176\#issuecomment-253496181

…erage) ### What is this PR for? Improved testing environment for zeppelin-web - added `test:watch` command for continuous testing - displaying coverage report in console - e2e testing in zeppelin-web (can be written easily compare to the zeppelin-server integration tests. For example: [home.spec.js](https://github.com/1ambda/zeppelin/blob/f90deb4bf3db57e36232c9c94ae3b07dfd7c2331/zeppelin-web/e2e/home.spec.js)) This PR adds [a zeppelin-web specific travis profile](https://github.com/1ambda/zeppelin/blob/ad08a3bc0da420f7a7b4771d1aee8bfdd962efa7/.travis.yml#L55) and it usually takes 8-9 mins to execute unit + e2e tests (zeppelin-web) - https://travis-ci.org/1ambda/zeppelin/jobs/252453901 #### Details - the headless chrome browser works with chromedriver 2.29+ (https://chromium.googlesource.com/chromium/src/+/c75dbfd25cc376b92a494d340259056a01e1432e) - in the case of ubuntu precise (our travis container), should use `/usr/bin/chromium-browser` - `xvfb` is required, please refer https://docs.travis-ci.com/user/gui-and-headless-browsers/#Using-xvfb-to-Run-Tests-That-Require-a-GUI and https://iamakulov.com/notes/install-google-chrome-on-travis/#what-does-the-code-mean - for protractor conf, please check travis-ci/travis-ci#7650 (comment) - can't install stable version of chrome, precise (12.04) support was dropped by chrome - chromium-browser (37.0) is shipped by default in precise and chromedriver version 2.11 is compatible with it. (https://support.saucelabs.com/hc/en-us/articles/225095307-Chromedriver-version-for-each-Chrome-browser-version, travis-ci/travis-ci#5899) ### What type of PR is it? [Improvement] ### Todos * [x] - `test:watch` * [x] - displaying coverage reports in console * [x] - e2e testing in zeppelin-web ### What is the Jira issue? [ZEPPELIN-2342](https://issues.apache.org/jira/browse/ZEPPELIN-2342) ### How should this be tested? CI should be green. If you want to test locally, - stop zeppelin which is running on localhost:8080 - `mvn package -DskipTests -DskipRat -Pweb-ci -B` - `mvn verify -DskipRat -pl 'zeppelin-web' -Pweb-ci -Pweb-e2e -B` #### Screenshots (coverage) ![image](https://user-images.githubusercontent.com/4968473/28031333-dc700c3a-65e1-11e7-96ca-582a9ffa97dd.png) #### Screenshots (e2e) ![image](https://user-images.githubusercontent.com/4968473/28032319-0e8b5adc-65e5-11e7-81ba-4e33c5f15bc0.png) ### Questions: * Does the licenses files need update? - NO * Is there breaking changes for older versions? - NO * Does this needs documentation? - YES, updated Author: 1ambda <1amb4a@gmail.com> Closes #2477 from 1ambda/ZEPPELIN-2342/differentiate-unit-and-integration-testing and squashes the following commits: ad08a3b [1ambda] fix: Restore all other pfoeils b6ff6d9 [1ambda] fix: Use 2.30 832cffb [1ambda] fix: Use 2.27 for chrome driver 4d82f03 [1ambda] fix: use 2.30 chromedriver 93cc90b [1ambda] fix: run unit test only when web-e2e enabled 0911afb [1ambda] fix: Update chromedriver version 893f67e [1ambda] fix: Set ignoreSync false for angular app 9b91ae2 [1ambda] fix: restore all other profiles dd300c2 [1ambda] fix: split if a5deed0 [1ambda] fix: Run xvf ni foreground 8d1ab5b [1ambda] fix: Remove sleep 3s 9a81fa1 [1ambda] fix: Add space between & and ; e924e76 [1ambda] fix: pass test, use 2 dists 58cfb23 [1ambda] fix: test 2 dist 0dc0304 [1ambda] fix: Use trusty for the second profile2 bf62085 [1ambda] fix: Remove version 61a7f9e [1ambda] fix: DO NOT USE CHROME_BIN 8926cd8 [1ambda] fix: use 2.11 9c20a44 [1ambda] fix: print chrome version f961a90 [1ambda] use before_install 9ed1e12 [1ambda] set info for test efc831c [1ambda] fix: remove headless db016a3 [1ambda] fix: use headless chrome in local 481528f [1ambda] fix: use precise 5a096da [1ambda] fix: use chromium-browser fcfa9c0 [1ambda] fix: required 282c83e [1ambda] fix: use beta 5a0d111 [1ambda] fix: use trusty 93fb571 [1ambda] fix: ls usr bin aff874f [1ambda] fix: use no-sandbox for sudo false contrainer 7d454a5 [1ambda] fix: Run xvfb in background 23e5670 [1ambda] fix: use beta chrome 3e9f494 [1ambda] fix: Use /usr/bin/chrome 55faa0e [1ambda] fix: Use google-chrome-stale 7da9845 [1ambda] WIP: Remove all other profiles a45f131 [1ambda] WIP: pass all tests 628ff34 [1ambda] fix: Set chromedriver version 763f3e2 [1ambda] fix: Set env 9450668 [1ambda] fix: redirect dbus into null bcac8a4 [1ambda] fix: Remove sandbox facf4c1 [1ambda] fix: Remove -X 20a8cfd [1ambda] fix: use no-sandbox 0662f92 [1ambda] fix: Set -X for web fc9d31f [1ambda] fix: Use CHROME_BIN2 4acb8e2 [1ambda] fix: Use CHROME_BIN 4699491 [1ambda] fix: Set info for e2e 905e6ad [1ambda] fix: Install chrome from source 7f5abfd [1ambda] fix: before_start 1f345ae [1ambda] fix: use headless dd115c3 [1ambda] fix: use direct connect 7d53d51 [1ambda] fix Remove chrome option eb9f0e8 [1ambda] fix: Set direct connect false 7c69f7a [1ambda] fix: Set chromeOnly for protractor d5e62e7 [1ambda] fix: Set chrome driver version https://github.com/angular/angular-cli/issues/2176\#issuecomment-253496181 f94a665 [1ambda] fix: Modify timeout for protractor 35b6fb1 [1ambda] WIP: Remove -X option to second job 5189807 [1ambda] chore: Add TEST_MODULES in travis.yml e354b1b [1ambda] chore: DO NOT rebuild web when e2e enabled b6d730f [1ambda] fix: echo commandsin travis.yml 6907c50 [1ambda] chore: Ingmore except web in test build 9f13d61 [1ambda] chore: Use usual test build command 4ef0a2c [1ambda] chore: Remove useless mvn setting 26ef708 [1ambda] fix: use prebuilt phantom f90deb4 [1ambda] chore: Move web e2e into zeppelin-web 40ac076 [1ambda] chore: New profile for e2e test only 7703615 [1ambda] WIP: Add -X to the second travis profile 0c2c1ec [1ambda] chore: Add web-e2e profile to mvn ca2b170 [1ambda] WIP: add -e mvn option to the second profile 0c09727 [1ambda] fix: Remove -X option from selenium profile 0907d72 [1ambda] chore: Ingnore protractor conf in RAT 2ed3973 [1ambda] fix: set gecko false for webdriver manager. See angular/webdriver-manager#216 eb447ef [1ambda] WIP: add -X log to selenium profioe 742bb96 [1ambda] chore: Exclude e2e specs from RAT b5a17a4 [1ambda] chore: Bind browser e2e test into CI process 76f4f58 [1ambda] docs: Update test section in zeppelin-web/README.md 15473de [1ambda] test: Add a basic e2e test for home 39dc77e [1ambda] chore: Add test:watch command e70281b [1ambda] feat: Use spec repoter and coverage

angular-automatic-lock-bot · 2019-09-06T09:41:09Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

filipesilva closed this as completed Oct 3, 2016

ecozoic mentioned this issue Oct 13, 2016

e2e test are stopped working - issue with selenium-webdriver PatrickJS/PatrickJS-starter#990

Closed

gkalpak mentioned this issue Nov 14, 2016

" E/launcher - Process exited with error code 199" error am getting when tried to run the protractor angular/angular-seed#381

Closed

1ambda referenced this issue in 1ambda/zeppelin Jul 11, 2017

fix: Set chrome driver version https://github.com/angular/angular-cli…

d5e62e7

…/issues/2176\#issuecomment-253496181

Bludwarf mentioned this issue Feb 22, 2019

Build Travis en échec à cause des tests Bludwarf/cuetube#142

Closed

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ng e2e fails with Error code 135 #2176

ng e2e fails with Error code 135 #2176

jtsom commented Sep 16, 2016

Please provide us with the following information:

amellnik commented Sep 20, 2016 •

edited

Loading

filipesilva commented Oct 3, 2016

jtsom commented Oct 3, 2016

ecozoic commented Oct 12, 2016

ecozoic commented Oct 13, 2016

alexpopdev commented Oct 13, 2016

jtsom commented Oct 13, 2016

ecozoic commented Oct 13, 2016

jtsom commented Oct 13, 2016

nestoru commented Oct 13, 2016

jtsom commented Oct 14, 2016

galicians commented Oct 21, 2016

mantisbayne commented Oct 24, 2016

IcodeNet commented Oct 26, 2016 •

edited

Loading

kevin-ashton commented Oct 26, 2016

mantisbayne commented Oct 26, 2016 •

edited

Loading

riddla commented Nov 8, 2016

riddla commented Nov 11, 2016

angular-automatic-lock-bot bot commented Sep 6, 2019

ng e2e fails with Error code 135 #2176

ng e2e fails with Error code 135 #2176

Comments

jtsom commented Sep 16, 2016

Please provide us with the following information:

amellnik commented Sep 20, 2016 • edited Loading

filipesilva commented Oct 3, 2016

jtsom commented Oct 3, 2016

ecozoic commented Oct 12, 2016

ecozoic commented Oct 13, 2016

alexpopdev commented Oct 13, 2016

jtsom commented Oct 13, 2016

ecozoic commented Oct 13, 2016

jtsom commented Oct 13, 2016

nestoru commented Oct 13, 2016

jtsom commented Oct 14, 2016

galicians commented Oct 21, 2016

mantisbayne commented Oct 24, 2016

IcodeNet commented Oct 26, 2016 • edited Loading

kevin-ashton commented Oct 26, 2016

mantisbayne commented Oct 26, 2016 • edited Loading

riddla commented Nov 8, 2016

riddla commented Nov 11, 2016

angular-automatic-lock-bot bot commented Sep 6, 2019

amellnik commented Sep 20, 2016 •

edited

Loading

IcodeNet commented Oct 26, 2016 •

edited

Loading

mantisbayne commented Oct 26, 2016 •

edited

Loading