# Previously successful Node build now only fails

**URL:** <https://discuss.circleci.com/t/previously-successful-node-build-now-only-fails/19394>\
**Category:** Bug Reports\
**Tags:** firefox, nodejs, docker\
**Created:** [January 16, 2018, 10:37pm UTC](https://discuss.circleci.com/t/previously-successful-node-build-now-only-fails/19394 "2018-01-16T22:37:58Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![maxamante](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/maxamante/32/17673_2.png) [@maxamante](https://discuss.circleci.com/u/maxamante)\
**Post date:** [January 16, 2018, 10:37pm UTC](https://discuss.circleci.com/t/previously-successful-node-build-now-only-fails/19394/1 "2018-01-16T22:37:58Z")

</div>

I’m configured to use node with browsers. There’s a `org.openqa.selenium.WebDriverException` that causes my build to fail where it wouldn’t before. To test, that it’s not my build, I pushed up my last good build and then pushed a README change that fails.

First line of failure:

```
 firefox 47 Tests failed: {"value":{"stacktrace":"org.openqa.selenium.WebDriverException: address not available\n...

```

My config:

```
docker:
  - image: circleci/node:8-browsers
working_directory: ~/repo

steps:
  ...
  - run:
      name: install JS dependencies
      command: |
        cd frontend/
        npm install
        npm run bower install
  ...
  - run:
      name: build and run JS tests
      command: |
        cd frontend/
        npm test
```

---

<div class="post-metadata">

**Author:** ![first87](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/first87/32/11905_2.png) [@first87](https://discuss.circleci.com/u/first87)\
**Post date:** [April 19, 2018, 6:15am UTC](https://discuss.circleci.com/t/previously-successful-node-build-now-only-fails/19394/2 "2018-04-19T06:15:14Z")

</div>

I also got the same issue.  
Can anyone provide any solution or workaround?

---

<div class="post-metadata">

**Author:** ![halfer](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/halfer/32/9083_2.png) [@halfer](https://discuss.circleci.com/u/halfer)\
**Post date:** [April 19, 2018, 11:09am UTC](https://discuss.circleci.com/t/previously-successful-node-build-now-only-fails/19394/3 "2018-04-19T11:09:41Z")

</div>

> [@first87](#):
>
> I also got the same issue.

That’s unlikely to be enough information to help someone help you. In general, browser test failure on CI should be debugged in the same way as the same happening locally.

Find out what “address not available” means. Does it mean you’re using a URL that is never available even when Selenium is up? Has the Selenium server gone down? Have you waited for it to start? Have you looked at your Selenium logs?

You can use the SSH feature to investigate this.

---

<div class="post-metadata">

**Author:** ![first87](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/first87/32/11905_2.png) [@first87](https://discuss.circleci.com/u/first87)\
**Post date:** [April 19, 2018, 11:30am UTC](https://discuss.circleci.com/t/previously-successful-node-build-now-only-fails/19394/4 "2018-04-19T11:30:04Z")

</div>

Ah ~ I missed to update my status.

In fact, I could resolve the issue by upgrading to the latest version of Firefox. Please refer to the following:

- [https://github.com/first87/hirst-dialog/issues/10](https://github.com/first87/hirst-dialog/issues/10)
- [https://github.com/first87/hirst-dialog/pull/12](https://github.com/first87/hirst-dialog/pull/12)

So if I can still ask a question, then can I run tests on a lower/specific version of browsers. i.e. Firefox 49, Chrome 60?

Thank you for further support in advance.

---

<div class="post-metadata">

**Author:** ![halfer](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/halfer/32/9083_2.png) [@halfer](https://discuss.circleci.com/u/halfer)\
**Post date:** [April 19, 2018, 11:34am UTC](https://discuss.circleci.com/t/previously-successful-node-build-now-only-fails/19394/5 "2018-04-19T11:34:39Z")

</div>

> [@first87](#):
>
> can I run tests on a lower/specific version of browsers. i.e. Firefox 49, Chrome 60?

I would expect so. I would do it by creating a custom Docker image containing the browsers and drivers required, and then using that instead of a prebuilt one from Circle. I do this with PhantomJS, and it works very well. You can then bump up the browsers in use on your own schedule, rather than suffer build breakage because something in the CircleCI image was upgraded.

---

<div class="post-metadata">

**Author:** ![first87](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/first87/32/11905_2.png) [@first87](https://discuss.circleci.com/u/first87)\
**Post date:** [April 19, 2018, 11:55am UTC](https://discuss.circleci.com/t/previously-successful-node-build-now-only-fails/19394/6 "2018-04-19T11:55:51Z")

</div>

Thank you for the hint.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [July 18, 2018, 11:55am UTC](https://discuss.circleci.com/t/previously-successful-node-build-now-only-fails/19394/7 "2018-07-18T11:55:53Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.