kyua-plain-tester: Configuration variables not supported;

[Craig Rodrigues]

Hi,

I tried kyua 0.10, and saw these:

kyua-plain-tester: Configuration variables not supported; ignoring
'has.cleanup=false'
kyua-plain-tester: Configuration variables not supported; ignoring
'unprivileged-user=tests'

Can kyua be changed so that these warnings are not printed out by default?
If not, how do I get rid of them?

Thanks.

--
Craig

[Julio Merino]

This is not new in 0.10 and in fact has been there since 0.5 or so.
Were you using an older version before or just started trying the
plain backend?

What's the harm caused by these warnings?

(But yes, they should be removed. Please file a bug.)

[Craig Rodrigues]

On Thu, Aug 14, 2014 at 6:34 PM, Julio Merino <jm...@meroh.net> wrote:
> This is not new in 0.10 and in fact has been there since 0.5 or so.
> Were you using an older version before or just started trying the
> plain backend?
>
> What's the harm caused by these warnings?
>

I'm using kyua, and introducing it to people who have not used it before,
and they are noticing these types of error messages and complaining.
These errors cause no harm, but when you are analyzing test results
looking for problems, they are unnecessary noise.

> (But yes, they should be removed. Please file a bug.)

https://github.com/jmmv/kyua/issues/104

Thanks.

--
Craig

[Garrett Cooper]

... until someone tries to figure out why unprivileged user tests
don't work :( (for example). These warnings should go away if/when the
TAP tester is taught to honor them and the variables get passed on to
the TAP tests (there's a bug open for that already --
https://github.com/jmmv/kyua/issues/84 ). I'll see what I can do to
make this work if Julio doesn't beat me to it first :).
Thanks!
-Garrett

[Julio Merino]

On Fri, Aug 15, 2014 at 1:18 AM, Garrett Cooper <yane...@gmail.com> wrote:

    ... until someone tries to figure out why unprivileged user tests
don't work :( (for example).

But they *do* work.

 

These warnings should go away if/when the
TAP tester is taught to honor them and the variables get passed on to
the TAP tests (there's a bug open for that already --
https://github.com/jmmv/kyua/issues/84 ). I'll see what I can do to
make this work if Julio doesn't beat me to it first :).

What doesn't work is what you described in #84: passing the value of the variables to the test program. This affects everything non-ATF.

The reason unprivileged_user appears here is because this configuration variable is special: ATF test programs once required being able to query its value and thus it was passed to them (and still is today for compatibility reasons).  And the warning refers to this.

(I don't know why has.cleanup appears here though; seems like a bug given that this certainly is not a configuration variable.)

--

Julio Merino | BCD / PD SRE | jm...@google.com | +1 (347) 694-0576