Hi Mike,
On 24/04/2020 02:33, Mike Kelsey wrote:
Quick question about running unit tests. I have all the EasyBuild stuff in
local clones, and set up the module to find them. Once I get my environment
set up, it points to my personal installation:
[kelsey@terra1 EasyBuild]$ which eb
/scratch/user/kelsey/EasyBuild/framework/eb
but when I launch the unit test per the documentation, I get complaints:
[kelsey@terra1 EasyBuild]$ export TEST_EASYBUILD_MODULES_TOOL=Lmod
[kelsey@terra1 EasyBuild]$ python -m test.framework.toy_build
WARNING: 'eb' not found in $PATH, failed to determine installation prefix!
WARNING: 'eb' not found in $PATH, failed to determine installation prefix!
WARNING: 'eb' not found in $PATH, failed to determine installation prefix!
[ repeated 6 times before '.' , with double blank lines between them! ]
Some of the individual test instances (the '.' marks) have many more such
warnings in between. I guess this is due to how many 'eb' invocations there
are per test?
Is there something I've missed in my setup? Is this a site issue?
Did you add the location of the 'eb' command to $PATH using 'export', or
not?
This may be an issue with the tests picking up the $PATH value that
doesn't have the location to the 'eb' command in there...
Feel free to open an issue for this, we can do better here with a little
bit of effort (looking for the 'eb' command relatively to test/ for
example).
regards,
Kenneth
-- Mike
