Cleber Rosa

Hi @nirGNU , just an update here regarding the release. I've found a few things (release related, no actual bugs in the code) that I need to address before cutting...

After quite a lot of work, we have the release jobs passing: https://github.com/avocado-framework/avocado/actions/runs/3325764602 The 92.1 release should be out Tomorrow.

@nirGNU [Avocado 92.1](https://pypi.org/project/avocado-framework/92.1/) is out! Closing this issue now.

The main problem we have to solve here is the one of testing across multiple repositories. With Avocado-VT, for instance, it tests itself with different Avocado versions, including the latest...

> > But, we lack the ideal situation on GitHub. > > Could you please elaborate here? > We can not trigger project "X"'s GH actions from a PR sent...

@kraxel thanks for reporting this issue. Interrupting the test and then moving the execution to the same (test) instance `tearDown()` method would be very hard to implement. I can see...

> option two shortcoming #1 -- seems to not be documented very well. Is there something more useful the object reference (which doesn't tell me how I can use it)...

> Hi @clebergnu I'm not 100% sure what is the task here. > > But what about using logging.config files here? Is that what you are thinking for this problem?...

Bitrot is real... and we've suffered with the main `avocado` man page. As much as Avocado should have man pages for all runners, it does feel like this will bitrot...

Maybe it's possible to remove the custom `.copr/Makefile` altogether? Or is 381ebee9c130f1bd76d791380229f68f1ee1525b about actually using `.copr/Makefile`?