Oh, feel free to review https://github.com/apache/geode/pull/3172.
Better suggestions on how to 'fix' the problem are most welcome.
On Thu, Feb 7, 2019 at 6:49 AM Jens Deppe wrote:
> The problem is caused by some change in test ordering (unit tests are
> running in parallel) which is resulting
The problem is caused by some change in test ordering (unit tests are
running in parallel) which is resulting in environmental pollution.
Probably Government shutdown related... :P
On Wed, Feb 6, 2019 at 7:31 PM Jens Deppe wrote:
> I didn't touch anything in this area, but nevertheless I revert
I didn't touch anything in this area, but nevertheless I reverted my commit
which preceded this failure (referenced in Owen's message). However, the
failure is still happening.
--Jens
On Wed, Feb 6, 2019 at 6:20 PM Owen Nichols wrote:
> There is a ticket for this,
> https://issues.apache.org/ji
There is a ticket for this, https://issues.apache.org/jira/browse/GEODE-6370
The problem “seems" to have started with this change:
commit 7f10f3a297eeeb473c3f16fff9465df9b404a21c
Date: Wed Feb 6 08:33:53 2019 -0800
GEODE-6364: Deploy of invalid jar file does not write file contents to
con
