Jan Richter

Because this was fixed by #5601 and it will be part of next release on Monday, I will close this. If anyone needs some additional information about it, feel free...

Since there is no activity on this topic for more than 2 years, I am closing this. @otisdog8 if you want to continue in this, feel free to reopen it.

Hi @amikan since you're already maintaining the downstream repo for this at https://salsa.debian.org/amikan/avocado, do you think that this and #5048 is still relevant for avocado upstream?

> Hello @richtja, this one is not relevant. If speaking about #5048, update of the libs can still be useful, but I'm afraid this won't be done properly in near...

Closing this based on the [discussion](https://github.com/avocado-framework/avocado/pull/5044#issuecomment-1905772227) in #5044

Hi @Naresh-ibm and @PraveenPenguin, thank you for this work, unfortunately this merge broke static-checks on master. Can you please fix it? Thanks.

@pevogam thanks for your comment, definitely the nrunner with processes=1 have to have all the avocado VT features of the legacy runner. Now I am still working on the bugs...

Hi @smitterl If those scripts are using the root logger, unfortunately yes the change is necessary, because now the avocado only captures messages from the Avocado namespace context.

Hi @PaulYuuu I am not sure what you are asking for, because the `avocado/core/test.py:Test` class already has `log` [property](https://github.com/avocado-framework/avocado/blob/master/avocado/core/test.py#L375) which points to the logger with `avocado.test` name space. So yes...

> However, it's not easy to get the `test` instances in some context, therefore I think we have to use other approaches instead. > > https://github.com/autotest/tp-qemu/blob/d0116d17a177bc10ee063a0917cb97b3aa0e0295/provider/cdrom.py#L146 Hi @luckyh, for those...