# Failing unit tests on a fresh fork **URL:** \ **Category:** Elasticsearch\ **Created:** [May 30, 2014, 12:13pm UTC](https://discuss.elastic.co/t/failing-unit-tests-on-a-fresh-fork/17834 "2014-05-30T12:13:33Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Patrick\_Peschlow](https://avatars.discourse-cdn.com/v4/letter/p/ac91a4/32.png) [@Patrick\_Peschlow](https://discuss.elastic.co/u/Patrick_Peschlow)\ **Post date:** [May 30, 2014, 12:13pm UTC](https://discuss.elastic.co/t/failing-unit-tests-on-a-fresh-fork/17834/1 "2014-05-30T12:13:33Z")
Hi, I forked Elasticsearch in order to test a possible bugfix and followed the instructions here [http://www.elasticsearch.org/contributing-to-elasticsearch/](http://www.elasticsearch.org/contributing-to-elasticsearch/). Unfortunately, running the unit tests of the fresh fork (commit 0e2d33b4a446af033db48284737a62b9cc8c99bb) via ES\_TEST\_LOCAL=true mvn clean test led to one of the randomized tests failing. I pulled a commit ( 9c98bb3554367c7a09aa6b01c0b7859d8ed3c018) that appeared in the meantime, tried again, and this time it was 2 tests failing. Is this expected behavior - it can just happen any time that you pull and the tests are broken? Or is there anything I need to do prior to running the tests that I might have missed? Regards, Patrick -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [May 30, 2014, 1:24pm UTC](https://discuss.elastic.co/t/failing-unit-tests-on-a-fresh-fork/17834/2 "2014-05-30T13:24:05Z")
Normally tests aren't broken but with randomized testing it is possible for things to sneak through. The best thing to do in this case is to submit an issue with the stack trace and the failing test. The stack trace will contain the randomized seed that'll be needed to reproduce the failure. Nik On Fri, May 30, 2014 at 8:13 AM, Patrick Peschlow \< [patrick.peschlow@codecentric.de](mailto:patrick.peschlow@codecentric.de)\> wrote: > Hi, > > I forked Elasticsearch in order to test a possible bugfix and followed the > instructions here > [http://www.elasticsearch.org/contributing-to-elasticsearch/](http://www.elasticsearch.org/contributing-to-elasticsearch/). > Unfortunately, running the unit tests of the fresh fork (commit > 0e2d33b4a446af033db48284737a62b9cc8c99bb) via > > ES\_TEST\_LOCAL=true mvn clean test > > led to one of the randomized tests failing. I pulled a commit ( > 9c98bb3554367c7a09aa6b01c0b7859d8ed3c018) that appeared in the meantime, tried > again, and this time it was 2 tests failing. > > Is this expected behavior - it can just happen any time that you pull and > the tests are broken? Or is there anything I need to do prior to running > the tests that I might have missed? > > Regards, > Patrick > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd29LFvVFZYpZEY9SXpgAi-1jYA7CP1u3GekyQmWxi%2BjzA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd29LFvVFZYpZEY9SXpgAi-1jYA7CP1u3GekyQmWxi%2BjzA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Patrick\_Peschlow](https://avatars.discourse-cdn.com/v4/letter/p/ac91a4/32.png) [@Patrick\_Peschlow](https://discuss.elastic.co/u/Patrick_Peschlow)\ **Post date:** [May 30, 2014, 2:56pm UTC](https://discuss.elastic.co/t/failing-unit-tests-on-a-fresh-fork/17834/3 "2014-05-30T14:56:04Z")
Thanks, just did that. Incidentally, in this particular case the fix was already made while I was opening the issue ๐Ÿ™‚ On Friday, May 30, 2014 3:24:39 PM UTC+2, Nikolas Everett wrote: > Normally tests aren't broken but with randomized testing it is possible > for things to sneak through. The best thing to do in this case is to > submit an issue with the stack trace and the failing test. The stack trace > will contain the randomized seed that'll be needed to reproduce the failure. > > Nik > > On Fri, May 30, 2014 at 8:13 AM, Patrick Peschlow \< > [patrick....@codecentric.de](mailto:patrick....@codecentric.de) \\> wrote: > > > Hi, > > > > I forked Elasticsearch in order to test a possible bugfix and followed > > the instructions here > > [http://www.elasticsearch.org/contributing-to-elasticsearch/](http://www.elasticsearch.org/contributing-to-elasticsearch/). > > Unfortunately, running the unit tests of the fresh fork (commit > > 0e2d33b4a446af033db48284737a62b9cc8c99bb) via > > > > ES\_TEST\_LOCAL=true mvn clean test > > > > led to one of the randomized tests failing. I pulled a commit ( > > 9c98bb3554367c7a09aa6b01c0b7859d8ed3c018) that appeared in the meantime, tried > > again, and this time it was 2 tests failing. > > > > Is this expected behavior - it can just happen any time that you pull and > > the tests are broken? Or is there anything I need to do prior to running > > the tests that I might have missed? > > > > Regards, > > Patrick > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/78f79843-9092-49b3-9434-96e2781c2ee3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/78f79843-9092-49b3-9434-96e2781c2ee3%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [May 30, 2014, 3:01pm UTC](https://discuss.elastic.co/t/failing-unit-tests-on-a-fresh-fork/17834/4 "2014-05-30T15:01:52Z")
When forking the master, things are expected to be quite volatile, and you should allow the ES core team a few hours or even days to let the dust settle down. Don't worry too much if things are temporarily broken on master, for stable builds, there are tagged releases... Jรถrg On Fri, May 30, 2014 at 4:56 PM, Patrick Peschlow \< [patrick.peschlow@codecentric.de](mailto:patrick.peschlow@codecentric.de)\> wrote: > Thanks, just did that. Incidentally, in this particular case the fix was > already made while I was opening the issue ๐Ÿ™‚ > > On Friday, May 30, 2014 3:24:39 PM UTC+2, Nikolas Everett wrote: > > > Normally tests aren't broken but with randomized testing it is possible > > for things to sneak through. The best thing to do in this case is to > > submit an issue with the stack trace and the failing test. The stack trace > > will contain the randomized seed that'll be needed to reproduce the failure. > > > > Nik > > > > On Fri, May 30, 2014 at 8:13 AM, Patrick Peschlow \< > > [patrick....@codecentric.de](mailto:patrick....@codecentric.de)\> wrote: > > > > > Hi, > > > > > > I forked Elasticsearch in order to test a possible bugfix and followed > > > the instructions here > > > [http://www.elasticsearch.org/contributing-to-elasticsearch/](http://www.elasticsearch.org/contributing-to-elasticsearch/). > > > Unfortunately, running the unit tests of the fresh fork (commit > > > 0e2d33b4a446af033db48284737a62b9cc8c99bb) via > > > > > > ES\_TEST\_LOCAL=true mvn clean test > > > > > > led to one of the randomized tests failing. I pulled a commit ( > > > 9c98bb3554367c7a09aa6b01c0b7859d8ed3c018) that appeared in the meantime > > > , tried again, and this time it was 2 tests failing. > > > > > > Is this expected behavior - it can just happen any time that you pull > > > and the tests are broken? Or is there anything I need to do prior to > > > running the tests that I might have missed? > > > > > > Regards, > > > Patrick > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047% > > > [40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5eb896bc-9242-4a2c-8d94-602101ba4047%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/78f79843-9092-49b3-9434-96e2781c2ee3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/78f79843-9092-49b3-9434-96e2781c2ee3%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/78f79843-9092-49b3-9434-96e2781c2ee3%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/78f79843-9092-49b3-9434-96e2781c2ee3%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH9SC%2BC-qpDhsCOWV7mAMLH7tBNQZ-HqR6G5Rp2%2BriQ-w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH9SC%2BC-qpDhsCOWV7mAMLH7tBNQZ-HqR6G5Rp2%2BriQ-w%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:25am UTC](https://discuss.elastic.co/t/failing-unit-tests-on-a-fresh-fork/17834/5 "2017-07-06T01:25:44Z")
Closed on July 6, 2017, 1:25am UTC