Ditto, after increasing the retry/delay all tests passed for me.

On 8/23/2016 10:10 AM, John Mazzitelli wrote:
Regarding the services itest failure with metric storage from the agent:

When running on my desktop, I don't even get that far - tests can't even start without timing out.

When running on my laptop (which is a faster machine with SSD), I confirmed the failure (ran it 2 times, failed the same way both times).

I changed this line:

https://github.com/hawkular/hawkular-services/blob/master/itest/src/test/java/org/hawkular/services/rest/test/AgentITest.java#L81

from: Retry.times(50).delay(100))
to:   Retry.times(50).delay(1000));

and ran it several times, all times it successfully passed.

So looks like a timing issue - the test just didn't wait long enough for the data to come in (which would explain the 204 it was getting). Moving it from 5s to 50s max timeout solved it for me.
_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev