| 2 | | Testing on an older VM, I got again 10 or so "failed" tests, all of which add something to do with the DM target ''dm-cache''. Reason: '''configure''' expects that '''modprobe''' can be found in $PATH. If it finds it, it sets MODPROBE_CMD to modprobe, otherwise, it leaves it empty. But since I build as much as possible as user, I have PATH=/usr/local/bin:/bin:/usr/bin:/opt/jdk/bin, and modprobe is not found. However the cache library in lvm2 uses MODPROBE_CMD to check or load the dm-cache module. Since it is empty, it finds that it is impossible to use the ''cache'' feature and marks the test as failed, although the test is run as root and now '''modprobe''' can be found in the PATH. So I think it should be wise to add '''path_append /sbin; path_append /usr/sbin''' before the configure command, maybe saving the PATH variable before. |
| | 2 | Testing on an older VM, I got again 10 or so "failed" tests, all of which had something to do with the DM target ''dm-cache''. Reason: '''configure''' expects that '''modprobe''' can be found in $PATH. If it finds it, it sets MODPROBE_CMD to modprobe, otherwise, it leaves it empty. But since I build as much as possible as user, I have PATH=/usr/local/bin:/bin:/usr/bin:/opt/jdk/bin, and modprobe is not found. However the cache library in lvm2 uses MODPROBE_CMD to check or load the dm-cache module. Since it is empty, it finds that it is impossible to use the ''cache'' feature and marks the test as failed, although the test is run as root and now '''modprobe''' can be found in the PATH. So I think it should be wise to add '''path_append /sbin; path_append /usr/sbin''' before the configure command, maybe saving the PATH variable before. |
