| Re: [kapua-dev] Build failures |
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!
Il giorno 26 apr 2017, alle ore 16:18, Morson, Stefano <stefano.morson@xxxxxxxxxxxx> ha scritto:
Yeah, cleaning the indexes before the tests is the right thing to do.
Thanks,Stefano
From: kapua-dev-bounces@eclipse.org <kapua-dev-bounces@xxxxxxxxxxx > on behalf of Jens Reimann <jreimann@xxxxxxxxxx>
Sent: Wednesday, April 26, 2017 3:27:27 PM
To: kapua developer discussions
Subject: Re: [kapua-dev] Build failures______________________________JensCheersSo I would suggest to re-enable this flag in the near future.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.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.
On Wed, Apr 26, 2017 at 3:11 PM, Morson, Stefano <stefano.morson@eurotech.com > wrote:
Hi all,
I temporarily added the property
-Dmaven.test.failure.ignore=true
to the Hudson build for Kapua. This is because there are tests (especially the datastore tests) that are recurrently failing in Hudson but are perfectly working on more than one the local machine. This could be due to the amount of available resources in Hudson. Uros will investigate more the resource usage.
Using the flag above we still have the evidence that something went wrong without invalidating the whole build. As soon as we'll have a remedy the flag will be removed.
Stefano
From: kapua-dev-bounces@eclipse.org <kapua-dev-bounces@xxxxxxxxxxx > on behalf of Morson, Stefano <stefano.morson@xxxxxxxxxxxx>
Sent: Tuesday, April 25, 2017 5:04:06 PM
To: kapua developer discussions
Subject: [kapua-dev] Build failuresHi all,
One of the issues we are having for the builds in these days was due to Sonar. I dropped an email to webmaster and he explained me this was due to a configuration change in the backends. He also fixed the issue in Kapua Hudson account so now we should be ok with this.
Stefano
Stefano Morson | EUROTECH | tel.: +39 0433 485411
_______________________________________________
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
--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
____________________________________________________________ _________________
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill
_________________
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
_______________________________________________
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