On Wed, Mar 1, 2017 at 8:48 PM Plamen Dimitrov <[email protected]>
wrote:
> On 03/01/2017 09:38 PM, Lucas Meneghel Rodrigues wrote:
> > To summarize, autotest heavily changes the loggers of its application and
> > core libraries to make it possible to transparently use
> >
> > import logging
> >
> > logging.info('foo')
> >
> > So that users and test writers don't have to. The base of this convoluted
> > logging setup was written a good 10 years ago, if I recall correctly.
> >
> > Nowadays we can simplify that custom handling, making it easier for
> > applications that only use autotest as a library, in this case,
> virt-test.
> > Lukas wants to propose this set of changes but was wondering how many
> > people nowadays run virt-test using autotest instead of using avocado, to
> > estimate the impact of the changes.
> >
>
> We make heavy use of autotest with virt-test and don't plan on moving to
> avocado soon. I didn't reply before because from the question it seemed
> that you are asking for people using autotest with avocado. In any case,
> I am just mentioning here for your information that we run a test suite
> on our custom server distribution using the two.
>
Hmm.... I think I made a mistake, Lukas' solution is actually going to be
implemented on the virt-test side, but that solution is going to impact
people driving virt-test through autotest, so no impact to Chris' team and
yours.
So Chris and the others, please disregard my previous message. That's what
you get when you try to catch up on e-mail after a long day of work, sorry
guys.
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
