Federico Beffa <be...@ieee.org> skribis: > One more thing: the function causing the test to fail is implemented > making use of ATLAS. However, the log does not show ATLAS being built > before numpy (as I would expect given the #:substitutable? #f > argument). If the machines to which hydra distributes the jobs are not > homogeneous, then it could be that the used ATLAS is not working > properly (maybe different ISA extensions?). If that is the case, then > why is the #:substitutable argument not honored?
I *think* that what happens, is that #:substitutable? also prevents offloading (because of <http://bugs.gnu.org/18747>.) So, since hydra.gnu.org currently runs the guix-daemon with --max-jobs=1, it probably ends up building ATLAS locally (this machine is a Quad-Core AMD Opteron(tm) Processor 2374 HE, but actually a VM.) However, numpy itself does get offloaded, so ATLAS from the step above ends up being transferred to whatever machine is building numpy, which could explain the problem. I’m not sure exactly what to do. Perhaps we should just exclude ATLAS and whatever refers to it from Hydra? > What machines is the build farm made of? Do they all have the same > version of OS and kernel? No, they’re different. The CPU and kernel are the only “impurities” that leak through the build environment though. It rarely matters, but ATLAS is clearly a case where it does make a difference. Thanks, Ludo’.
