Hi, I've just run the testsuite and got a couple of failures.
The first I can't solve is 30.1 FAILURE: there was an error during the rpmbuild spawn ls /tmp/built_rpms/RPMS spawn /usr/bin/bash -c exec rpm -qpl /tmp/built_rpms/RPMS//Slurm-0-0..rpm | grep srun.1 error: open of /tmp/built_rpms/RPMS//Slurm-0-0..rpm failed: No such file or directory FAILURE: srun.1 was put in the wrong place spawn /usr/bin/bash -c exec rpm -qpl /tmp/built_rpms/RPMS//Slurm-0-0..rpm | grep srun error: open of /tmp/built_rpms/RPMS//Slurm-0-0..rpm failed: No such file or directory FAILURE: srun was put in the wrong place spawn /usr/bin/bash -c exec rpm -qpl /tmp/built_rpms/RPMS//Slurm-0-0..rpm | grep slurmctld error: open of /tmp/built_rpms/RPMS//Slurm-0-0..rpm failed: No such file or directory FAILURE: slurmctld was put in the wrong place FAILURE: In phase one of the rpmbuild test30.1 FAILURE Is this expected? (I have successfully compiled the RPMs on this system - it's how I'm running the tests) Oh, I've just noticed that 32.5 failed as well. Is one of the cluster-wide file systems alluded to in the README (slurm-16.05.0/testsuite/expect/README) meant to be /tmp? I have a cluster wide file system, and I'm running the software from there. But /tmp isn't part of it. Should I make /tmp cluster wide? cheers L. ------ The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper
