https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7988
--- Comment #6 from Kevin A. McGrail <[email protected]> --- (In reply to Henrik Krohns from comment #5) > (In reply to Sidney Markowitz from comment #4) > > (In reply to Kevin A. McGrail from comment #1) > > > Just one note that I believe the root flag was added back when the tests > > > would possibly slam a production instance of something like spamd running > > > on > > > the same system on the same port. > > > > I'm open to the argument that having to set the run_root_tests flag in > > config.dist or run using prove with a --override will be useful to ensure > > that someone does not unthinkingly run sudo make test TEST_FILES="t/root*.t" > > or even sudo make test on a production server. > > > > I personally wouldn't do it, but I'm not a sysadmin in a production > > environment, so what do I know? > > Regardless of any flags, the tests should be made sure they won't affect any > external spamd or write things outside of test directory. At quick glance, > only spamd_prefork_stress* makes a dumb generic "pkill -f spamd child". 100% agreed and why I wanted to flag the issue with changing xt. Those tests are run really only by RM's with and without privileged access. They are not for the faint of heart to just run normally and could impact production systems they way they are written now. There's been improvements especially around the sudo tests but I documented the how I built a release box in the build/README to try and help other RMs spin up something for testing. -- You are receiving this mail because: You are the assignee for the bug.
