On 5/2/17, 2:07 AM, "Tom Chiverton" wrote:
>Sounds easy.
>
>In the mean time, I think the instance has died ? Can you restart it ?
When I looked it appeared to be up, but still stuck on MD5Checker even
though I updated it last night. It turned out that the ASF CMS didn't
pick up the changes s
Sounds easy.
In the mean time, I think the instance has died ? Can you restart it ?
Tom
On 02/05/17 02:18, Alex Harui wrote:
On 4/30/17, 7:44 AM, "Christofer Dutz" wrote:
Hi Gyus,
I guess the reason is that the default Ant job tries to read the file
into memory. This isn’t needed in orde
On 4/30/17, 7:44 AM, "Christofer Dutz" wrote:
>Hi Gyus,
>
>I guess the reason is that the default Ant job tries to read the file
>into memory. This isn’t needed in order to calculate the md5 hash … If
>the target used a streaming implementation, it should work with a few KB
>of memory.
True.
erton mailto:t...@extravision.com>>
Reply-To: "dev@flex.apache.org<mailto:dev@flex.apache.org>"
mailto:dev@flex.apache.org>>
Date: Friday, April 28, 2017 at 2:51 AM
To: "dev@flex.apache.org<mailto:dev@flex.apache.org>"
mailto:dev@flex.apache
Reply-To: "dev@flex.apache.org<mailto:dev@flex.apache.org>"
mailto:dev@flex.apache.org>>
Date: Friday, April 28, 2017 at 2:51 AM
To: "dev@flex.apache.org<mailto:dev@flex.apache.org>"
mailto:dev@flex.apache.org>>
Subject: MD5 checker Jenkins job
The Jenkins j
The Jenkins job that checks for new MD5s is choking on "verifying
checksum" but I can't see where that actually is because it's an out of
memory error and crashed in flash.net.URlStream.readBytes
I've just closed it for now...
--
*Tom Chiverton*
Lead Developer
e: t...@extravision.com