And cite has now passed - so we are back in the game.
version = 2.10-SNAPSHOT
git revision = 6fb4c93df94326a9939dba371a5040e03f127a5b
git branch = origin/2.10.x
build date = 26-Oct-2016 21:22
geotools version = 16-SNAPSHOT
geotools revision = b7852cddc7079d0dfe5d7c37203b925aa1ef6deb
geowebcache ve
Yep, I can confirm that now Geotools 16.x builds fine on my laptop, thanks
Devon!
On Wed, Oct 26, 2016 at 9:49 PM, Jody Garnett
wrote:
> Thanks, merged and backported, release should be back on.
>
> --
> Jody Garnett
>
> On 26 October 2016 at 11:15, Devon Tucker wrote:
>
>> Hello all,
>>
>> Apo
Thanks, merged and backported, release should be back on.
--
Jody Garnett
On 26 October 2016 at 11:15, Devon Tucker wrote:
> Hello all,
>
> Apologies for the issue. I have a PR ready for a workaround:
>
> https://github.com/geotools/geotools/pull/1365
>
> Not ideal, but I tried what I thought w
Hello all,
Apologies for the issue. I have a PR ready for a workaround:
https://github.com/geotools/geotools/pull/1365
Not ideal, but I tried what I thought would be the simplest fix and it
didn't work. Unfortunately configuration initialization for ImageMosaic is
a bit messy.
Let me know if th
Ah!
I experienced the same failure while preparing this PR:
https://github.com/geotools/geotools/pull/1363
Then I noticed the Travis build was passing and I thought the failure was
specific to my laptop... seems like it's not.
On Wed, Oct 26, 2016 at 6:20 PM, Ian Turton wrote:
>
>
> Here i
Here is the screen shot of the failing test images -
Failed tests:
HeterogenousCRSTest.testHeterogeneousCRS:56->testMosaic:105 Images are
visibly different, found 2147483647 different pixels, against a threshold
of 1000
Ian
--
Ian Turton
--