Hi,
it’s NOT true since the datastore unit tests are searching for messages in the specific channel and for a specific date range. So, even if all the test are running concurrently, every test should find only the right messages.
Moreover some failures are due to a timeout occurring in the store phase. So it means that es instance it’s not able to store a message after 60 seconds!
Yeah, cleaning the indexes before the tests is the right thing to do.
Thanks,
Stefano
I think I fixed most of those issues with the datastore tests.
Beside the index "refresh" issue, which I mentioned and added there was some assumptions that the data found in those indices actually is only coming from the unit test in question. However running one unit test after each other filled up the storage an messed
up the other tests. So running a single unit test works, but running all of them doesn't. Adding the refresh call actually broke it locally and on hudson, as it seems to me those tests never really worked when running batched.
I fixed this by clearing out all indices before each unit test and now it works. This fixed it locally, on travis and should also work on hudson.
So I would suggest to re-enable this flag in the near future.
Cheers
Jens
_______________________________________________
kapua-dev
mailing list
kapua-dev@xxxxxxxxxxx
To
change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev
|