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.
On Wed, Mar 1, 2017 at 3:10 PM Chris Evich <[email protected]> wrote:
> On 02/28/2017 11:23 AM, Lukáš Doktor wrote:
> > I sent this originally to Avocado but this list is probably more
> > appropriate. I'm wondering if anyone is still using Autotest and traces
> > the latest virtest from Avocado-vt. I'd like to propose a change to
>
> YES!, (as you may guess) Autotest is used heavily in Docker testing. I
> don't know/care about virttest, but certainly we can't have any
> disruptive changes happening in Autotest. My team depends on it's
> "maintenance mode" state as a (virtual) guarantee of stability.
>
> What does the 'change to logging' entail? Is there code or a PR I can
> test against?
>
> Thanks for the heads-up.
>
> --
> Chris Evich, RHCA, RHCE, RHCDS, RHCSS
> Quality Assurance Engineer
> To err is human, to blame somebody else is more, to tell you so is QA.
>
> _______________________________________________
> Autotest-kernel mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/autotest-kernel
>
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
