On 08/02/2018 11:18, Jakob Schiøtz wrote:
Hi Pieter,
I have seen something similar with one of my own configs. Do you depend
explicitly on Python, or implicitly through another easyconfig. I think
%(pyvers)s is only substituted if you depend explicitly on Python.
This is most likely the problem, you indeed need to depend on Python
directly to ensure that %(pyver)s is resolved.
Or it may be a bug related to EASYBUILD_VERIFY_EASYCONFIG_FILENAMES=‘True’,
which I have never tried.
It could be a bug, but it's unlikely, we would have known by now I think...
regards,
Kenneth
Best regards
Jakob
On 6 Feb 2018, at 1:36, Pieter Neerincx <[email protected]> wrote:
Hi all,
We are using EasyBuild 3.5.1 with
export EASYBUILD_VERIFY_EASYCONFIG_FILENAMES='True'
Worked like a charm so far and prevented us several times from deploying
something that would fail miserably when used as a dependency during dependency
resolution with the robot function, but I'm now getting this error:
ERROR: Easyconfig filename 'TensorFlow-1.5.0-foss-2015b-Python-3.6.3.eb' does
not match with expected filename
'TensorFlow-1.5.0-foss-2015b-Python-%(pyver)s.eb' (specs: name: 'TensorFlow';
version: '1.5.0'; versionsuffix: '-Python-%(pyver)s'; toolchain name, version:
'foss', '2015b')
(Forget about that TensorFlow EasyConfig, which is work in progress and more of
an temporary workaround using the CmdCp EasyBlock and some shell scripting.)
Is it expected behaviour that %(pyver)s is not substituted before checking if
the EasyConfig filename matches the expected pattern or should a file a bug
report or ...?
Cheers,
Pi
-------------------------------------------------------------
phone: +31 6 143 66 783
e-mail: [email protected]
skype: pieter.online
-------------------------------------------------------------
--
Jakob Schiøtz, professor, Ph.D.
Department of Physics
Technical University of Denmark
DK-2800 Kongens Lyngby, Denmark
http://www.fysik.dtu.dk/~schiotz/
