Re: geode-assembly fails with SIGABRT

Kirk: what happens when you run ./gradlew :geode-assembly:docker in your local dev environment? Does it break the same way? If not, then I surmise this may be due to a recent configuration change to the AWS AMI used for CI. This bug report on Docker credentials helper has some stack traces that lo

Problem in rolling upgrade since 1.12

Hi, I have observed that since version 1.12 rolling upgrades to future versions leave the first upgraded locator "as if" it was still on version 1.12. This is the output from "list members" before starting the upgrade from version 1.12: Name | Id |

Re: Is "java" available to acceptanceTests?

Here's a link to the precheckin failure: https://concourse.apachegeode-ci.info/builds/163281 On Fri, Jun 5, 2020 at 3:16 PM Kirk Lund wrote: > Does the image(s) we use for running acceptanceTest include "java"? I've > written some new AcceptanceTests for the LocatorLauncher and ServerLauncher >

geode-assembly fails with SIGABRT

The docker image (or something related) seems to be broken for geode-assembly. Anyone working on fixing this or know how to fix it? https://concourse.apachegeode-ci.info/builds/163375 Something in the docker setup SIGABRTs... > Task :geode-assembly:docker free(): invalid pointer SIGABRT: abort P

Is "java" available to acceptanceTests?

Does the image(s) we use for running acceptanceTest include "java"? I've written some new AcceptanceTests for the LocatorLauncher and ServerLauncher which pass locally but fail in precheckin in the cloud with *java.io.IOException: Cannot run program "java"*. > Task :geode-assembly:acceptanceTest