I have gotten a lot of good feedback about FATE since I released the core fate-script.py program last week. I have posted a new version of fate-script.py and its config file, fateconfig.py-example, that includes a few new features:
- Config file now has a NICE_LEVEL option which, when set to a numeric value, will re-nice the script to a nicer level. This is in consideration to certain testers who are trying to obtain permission to run FATE continuously on shared systems.
- Setting the LD_LIBRARY_PATH used to be an explicit part of the script. It is now user-configurable (well, it’s open source, so it’s always configurable; it’s just more easily configurable now) through the config file. This was added since Windows targets do not honor LD_LIBRARY_PATH. This is one more step on the path to getting Cygwin/MinGW configurations into FATE.
Further, I fixed a bug with the timeout killer in the FATE script. Well, “fix” is a strong word (“wrongheaded hack” is more accurate). But the end result is that FATE will honor the individual test spec timeouts in order to guard against infinite loops that may creep into SVN.
Well cygwin should support LD_LIBRARY_PATH, but I never manage to make it works…
hmmm, forget it, I was thinking of LD_PRELOAD…
Hm, I think it would be better if you set the LD_LIBRARY_PATH in a way to works for most people by default, i.e. so it behaves as before by default – it should never make things worse than not setting it.
And what about a generic way to set any variable for the script?
Generic way to set any environment variable? That can be arranged fairly easily.
I believe LD_LIBRARY_PATH, LD_PRELOAD are ELF-isms.
Dynamic libraries on Windows (Cygwin too) are searched on current directory and in PATH. Hence I would say PATH is the environment variable to be set.