Actually I just noticed that it was the tell-based protocol (with that
ClientBackedDataStore)
run of that test that failed. DistributedDataStoreIntegrationTest is
parameterized to run all the test cases twice - once with the existing
ask-based protocol and the second with the new tell-based protoco
Yeah… maybe we should set up a stress test to find it. I guess we can also
just assume since it hasn't failed carbon before it won't do that again.
--Colin
On Thu, Apr 13, 2017 at 7:15 PM, Thanh Ha
wrote:
> I think it's intermittent (although should be fixed if it is) since my
> rebuild [0] ha
I think it's intermittent (although should be fixed if it is) since my
rebuild [0] has built past the point of this failure.
Regards,
Thanh
[0]
https://jenkins.opendaylight.org/releng/job/autorelease-release-carbon/243/
On Thu, Apr 13, 2017 at 9:58 PM, Colin Dixon wrote:
> Tom, do you think yo
Tom, do you think you can take a look at this to see if it's a real failure?
--Colin
On Thu, Apr 13, 2017 at 5:54 PM, Jenkins wrote:
> Attention controller-devs,
>
> Autorelease carbon failed to build sal-distributed-datastore from
> controller in build
> 242. Attached is a snippet of the erro
Attention controller-devs,
Autorelease carbon failed to build sal-distributed-datastore from controller in
build
242. Attached is a snippet of the error message related to the
failure that we were able to automatically parse as well as console logs.
Console Logs:
https://logs.opendaylight.org/