# Selenium tests timing out

**URL:** <https://discuss.circleci.com/t/selenium-tests-timing-out/7765>\
**Category:** Bug Reports\
**Tags:** selenium, chrome\
**Created:** [October 31, 2016, 11:24am UTC](https://discuss.circleci.com/t/selenium-tests-timing-out/7765 "2016-10-31T11:24:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dominik](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@Dominik](https://discuss.circleci.com/u/Dominik)\
**Post date:** [October 31, 2016, 11:24am UTC](https://discuss.circleci.com/t/selenium-tests-timing-out/7765/1 "2016-10-31T11:24:27Z")

</div>

We run some functional tests in chrome using selenium through nightwatch.js. We’re running selenium 3.0.1 and chromedriver 2.24.

The problem is that roughly half of the time the build times out while running these tests. No error is shown and we don’t encounter that problem locally or on Travis CI, which makes me suspect it might be an issue with Circle Ci. When I killed either selenium or chrome when testing locally, it produced an error that was logged to the terminal.

I’m happy to provide more information if needed. Hope someone knows how to solve this issue.

---

<div class="post-metadata">

**Author:** ![tom](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/tom/32/27680_2.png) [@tom](https://discuss.circleci.com/u/tom)\
**Post date:** [November 25, 2016, 2:15pm UTC](https://discuss.circleci.com/t/selenium-tests-timing-out/7765/2 "2016-11-25T14:15:58Z")

</div>

Can you add the following environment variable to your project:

```auto
DBUS_SESSION_BUS_ADDRESS = /dev/null

```

You can do this via the CircleCI UI: Project settings \> Environment Variables

Or in `circle.yml`:

```auto
machine:
  environment:
    DBUS_SESSION_BUS_ADDRESS: /dev/null

```

Do let us know if that helps or not. Our testing suggests that this resolves issues related to x11-dbus and Xvfb in containerized environments with flaky browser testing using Selenium, Chrome / Firefox.

---

<div class="post-metadata">

**Author:** ![Dominik](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@Dominik](https://discuss.circleci.com/u/Dominik)\
**Post date:** [November 25, 2016, 2:47pm UTC](https://discuss.circleci.com/t/selenium-tests-timing-out/7765/3 "2016-11-25T14:47:10Z")

</div>

Thanks for the help. We for now fixed the issue by using a new [PR](https://github.com/nightwatchjs/nightwatch/pull/1232) for our testing framework that handles timeouts in session retrieval more gracefully. We still will try out your suggestion though (it’s even better if there are now timeouts in the communication with selenium to begin with).

---

<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:** [June 18, 2018, 11:34am UTC](https://discuss.circleci.com/t/selenium-tests-timing-out/7765/4 "2018-06-18T11:34:27Z")

</div>

Closed on June 18, 2018, 11:34am UTC