I explicit disabled some distros that were doing that in the past weeks.
Can't recall how many, but I got the problem because the non-root user
running the smoker wasn't able to remove temporary files created during
the distro 'make phase' or files created during the tests.
Those guys also generated several security warnings when executing under
OpenBSD (in the form of e-mails sent periodically to the accounts under
the wheel group).
Running unknown code is dangerous enough without root access, using a VM
or not.
Em 04/12/2017 20:48, David Cantrell escreveu:
On 04/12/2017 18:52, Slaven Rezic wrote:
Yes, that's from the test suite of my new module. Unfortunately there
does not seem to be a possibility to check whether sudo (password-less)
is possible without actually trying to run it and generate this security
message. The sudo-using tests make sense in some environments (e.g. on
travis-ci with sudo=true), but if testers find it too annoying I can
move them to xt/ and run them only on systems where it actually works.
If the test is sudo-specific then I don't have anything useful to say,
but if it's just that some tests require root then take a look at
File::Find::Rule::Permissions for a work-around I put in my tests.
Anyone foolish enough to run all the tests as root will run them all, as
will travis and my jenkins box, anything else will just skip those tests.
