ImageMagick latest

[Fernando de Oliveira]

Latest at the moment is:

​ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick-6.9.0-6.tar.xz

Waiting for freeze to use latest at the occasion.

Opinions, please?

[Fernando de Oliveira]

Fixed at r15548.

Leaving open, because I made a text change in the tests (check and validate) and am not sure if it is in good English.

Please, after checking/fixing, close it.

[bdubbs@…]

The build and make check are fine. The only issue I have is the times. I got .846 SBU for the standard build (-j5). That's not a problem, but I got 3m41s for the validate tests -- or about 2.2 SBU. That's a lot faster than you got. I watched it using top and it was only using one core.

validation suite: 5320 tests; 5320 passed; 0 failed.

The wording is fine, closing. I'll tag it for 7.7.

[Fernando de Oliveira]

Thanks.

Notice that here, 6490 tests are performed, compare with 5320 tests. Probably some more optional dependencies, here.

Today's run, including build, install and validate, took SBU_TIME: 25.20809248, all with -j1.

Ran today, just to check, here are both results ( 1 SBU = 173s ):

$ tail -n10 /tmp/imagemagick-6.9.0.6-validate-2015.02.20-18h17m00s.log \
            /tmp/imagemagick-6.9.0.6-validate-2015.02.25-07h21m13s.log
==> /tmp/imagemagick-6.9.0.6-validate-2015.02.20-18h17m00s.log <==
validation suite: 6490 tests; 6490 passed; 0 failed.

real    51m36.635s
user    14m34.156s
sys 14m30.948s

33M ../DEST-imagemagick-6.9.0.6
147M    ../ImageMagick-6.9.0-6
179M    total
~/tmp/porg-build-2015.02.20-18h17m00s/ImageMagick-6.9.0-6

==> /tmp/imagemagick-6.9.0.6-validate-2015.02.25-07h21m13s.log <==
validation suite: 6490 tests; 6490 passed; 0 failed.

real    65m24.940s
user    15m16.743s
sys 14m3.102s

33M ../DEST-imagemagick-6.9.0.6
118M    ../ImageMagick-6.9.0-6
150M    total
~/tmp/porg-build-2015.02.25-07h21m13s/ImageMagick-6.9.0-6

First results where via ssh. Second, in LXDE.

System load was always over 1. Processor use changed all the time. In both runs, what strikes me is that the terminal output stopped always in the middle of the last line, then after some time, about 8 to 10 lines were written at once, again with the last one incomplete, and so on.

During the tests, the system becomes very unresponsive. As this is a VM, and you must have run with NVidia, noticing the tests are always with graphics data, perhaps this is the reason for the difference, the gpu doing most of the job, there.

[Fernando de Oliveira]

Forgot to write that hd space needed is larger than build dir size, because the tests use temporary directories in /tmp, which are created and deleted during the tests.

[bdubbs@…]

Replying to fo:

As this is a VM, and you must have run with NVidia, noticing the tests are always with graphics data, perhaps this is the reason for the difference, the gpu doing most of the job, there.

I ran via ssh, but on bare metal. The Nvidia card I have in that system is not an expensive one, but is new. I think the main difference would be the VM, although the GPU could have an impact.