+1
built and ran tests for native client on windows.
-michael
On Wed, Oct 16, 2019 at 2:21 PM Blake Bender wrote:
> Okay I'm convinced we're okay, so switching to a +1. Standard PEBKAC error
> here, I managed to produce a native client build which was missing the jar
> file we use for a
No worries and thanks for taking the time to look at the bits!
--Jens
On Wed, Oct 16, 2019 at 2:21 PM Blake Bender wrote:
> Okay I'm convinced we're okay, so switching to a +1. Standard PEBKAC error
> here, I managed to produce a native client build which was missing the jar
> file we use for
Okay I'm convinced we're okay, so switching to a +1. Standard PEBKAC error
here, I managed to produce a native client build which was missing the jar
file we use for a whole bunch of tests, so all failed.
Thanks,
Blake
On Wed, Oct 16, 2019 at 1:03 PM Blake Bender wrote:
> I'm a -1 on this
I'm a -1 on this one, for the time being, sorry. I ran native client
integration tests against it on my dev workstation and am seeing an
inordinate number of failures. It's gonna take me some time to understand
what's going on, but I'll update everyone shortly as to whether I think we
have a
Hi,
Thanks for your suggestion, Anthony. I gave it a try and the rolling downgrade
worked because peers are prepared to exchange messages in different versions by
means of the toDataPre_GEODE_X_X_X_X() fromDataPre_GEODE_X_X_X_X mechanism.
After all my investigation on this topic I have come to
