[GitHub] jena issue #329: Give more time to ElasticSearch to startup

2017-12-17 Thread ajs6f
Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/329 Ah, I think I figured it out-- for future reference, this seems to happen when you merge a branch into `master` and push it, but the branch on Github isn't up to date with the local repo. Okay, I should

[GitHub] jena issue #329: Give more time to ElasticSearch to startup

2017-12-17 Thread ajs6f
Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/329 Dang it! This is the second time this has happened. I've been merging my PR branches into `master` and then pushing them. It normally works fine... I need to figure out what's nutty on my end. In the

[GitHub] jena issue #329: Give more time to ElasticSearch to startup

2017-12-17 Thread afs
Github user afs commented on the issue: https://github.com/apache/jena/pull/329 There is a different commit ee9c98b108942f258fd9a6b2e02cc6104a648368 on the Jena ASF git repository. This can be closed? For next time, it would be good to use the same commit: