# ES tests taking very long to execute (\> 1800s) on Windows 10

**URL:** <https://discuss.elastic.co/t/es-tests-taking-very-long-to-execute-1800s-on-windows-10/97929>\
**Category:** Elasticsearch\
**Created:** [August 22, 2017, 2:46pm UTC](https://discuss.elastic.co/t/es-tests-taking-very-long-to-execute-1800s-on-windows-10/97929 "2017-08-22T14:46:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![saralor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saralor/32/21330_2.png) [@saralor](https://discuss.elastic.co/u/saralor)\
**Post date:** [August 22, 2017, 2:46pm UTC](https://discuss.elastic.co/t/es-tests-taking-very-long-to-execute-1800s-on-windows-10/97929/1 "2017-08-22T14:46:24Z")

</div>

I've forked the source code for ES to try and start playing with it. Before that, I'd like to verify that everything is at a stable point, so I'm running the tests with `gradle check`.

The problem is that it always takes a very long time, until a timeout is reached and it quits.

`12:14:27.629 [LIFECYCLE] [org.gradle.api.Task] > Throwable #1: java.lang.Exception: Test abandoned because suite timeout was reached.`

`12:14:27.721 [LIFECYCLE] [org.gradle.api.Task] > Throwable #1: java.lang.Exception: Suite timeout exceeded (>= 1800000 msec).`

This happens every single time, and while I could increase the time out, I assume tests should not take that long. I'm running on a Windows 10 machine with 8GB RAM.

Any idea?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 19, 2017, 2:46pm UTC](https://discuss.elastic.co/t/es-tests-taking-very-long-to-execute-1800s-on-windows-10/97929/2 "2017-09-19T14:46:41Z")

</div>

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