*amend* parameters ignored? just wondering if there is something else to it

[fgeorgatos]

(I know, this is a hopeless way to overcome the checksum control which HAS to be done manually,
but the failure mode is interesting in its own right, because it bails out in a totally unexpected manner,
without actually amending anything in the original file?!)

[easybuild2@localhost easybuild]$ time eb cuDNN-6.0-CUDA-8.0.61.eb --try-amend=parallel=1 --amend=checksums=a08ca487f88774e39eb6b0ef6507451d --modules-tool=EnvironmentModulesC --module-syntax=Tcl -r
== temporary log file in case of crash /tmp/eb-woRm0B/easybuild-J_wpKY.log
== resolving dependencies ...
== processing EasyBuild easyconfig /scratch/EB3.2.0_4DL2/el7/0.1.0-86-gdec7b3e/software/EasyBuild/3.2.0/lib/python2.7/site-packages/easybuild_easyconfigs-3.2.0-py2.7.egg/easybuild/easyconfigs/c/cuDNN/cuDNN-6.0-CUDA-8.0.61.eb
== building and installing cuDNN/6.0-CUDA-8.0.61...
== fetching files...
== creating build dir, resetting environment...
== unpacking...
== FAILED: Installation ended unsuccessfully (build directory: /home/easybuild2/.local/easybuild/build/cuDNN/6.0/dummy-dummy-CUDA-8.0.61): build failed (first 300 chars): Checksum verification for /home/easybuild2/.local/easybuild/sources/cudnn-8.0-linux-x64-v6.0.tgz using 4aacb7acb93c5e4dfa9db814df496219 failed.
== Results of the build can be found in the log file(s) /tmp/eb-woRm0B/easybuild-cuDNN-6.0-20170514.145801.sElPD.log
ERROR: Build of /scratch/EB3.2.0_4DL2/el7/0.1.0-86-gdec7b3e/software/EasyBuild/3.2.0/lib/python2.7/site-packages/easybuild_easyconfigs-3.2.0-py2.7.egg/easybuild/easyconfigs/c/cuDNN/cuDNN-6.0-CUDA-8.0.61.eb failed (err: 'build failed (first 300 chars): Checksum verification for /home/easybuild2/.local/easybuild/sources/cudnn-8.0-linux-x64-v6.0.tgz using 4aacb7acb93c5e4dfa9db814df496219 failed.')

real    0m1.428s
user    0m1.138s
sys     0m0.297s

[boegel]

@fgeorgatos Can you clarify, what are you expecting to happen here exactly using --amend=checksums=... (rather than --try-amend)?

I'm not sure that values passed to --amend are used at all when you're also specifying an easyconfig file to use, so we should probably make that clear via an error or warning...

[fgeorgatos]

@boegel : correct, either fail or warn, would be great.

[boegel]

@fgeorgatos Can you check using --try-amend rather than --amend?

I think --amend is only used to filter candidate easyconfigs (which is not done here because you're specifying one).