| 1 |
Ryan Hill <dirtyepic@g.o> writes: |
| 2 |
|
| 3 |
>> Also relevant question: some tests require root privileges. What we |
| 4 |
>> should do in such case? |
| 5 |
> |
| 6 |
> When I asked this previously I was told to check the current user's |
| 7 |
> permissions before running them. I haven't had a case where I've had |
| 8 |
> to though. |
| 9 |
|
| 10 |
On libarchive there has been some tests requiring root privileges; the |
| 11 |
temporary way out was to disable those tests, and the final way out has |
| 12 |
been working with upstream so that the testsuite itself detects whether |
| 13 |
you have root privileges or not and decides to skip the tests that |
| 14 |
cannot be applied. |
| 15 |
|
| 16 |
Just to say. |
| 17 |
|
| 18 |
In general I think it makes sense to be able to run _most_ of the tests |
| 19 |
as user, and discard the ones that cannot be run without root privileges |
| 20 |
(I expect most software not to require root privileges for the tests, |
| 21 |
it's silly to unless you need to work with file permissions or stuff |
| 22 |
like that). |
| 23 |
|
| 24 |
-- |
| 25 |
Diego "Flameeyes" Pettenò |
| 26 |
http://blog.flameeyes.eu/ |
Archives