Open Stack

 ---- On Tue, 22 Mar 2022 08:09:49 -0500 Luigi Toscano <ltoscano at redhat.com> wrote ----
 > On Tuesday, 22 March 2022 13:18:03 CET Sean Mooney wrote:
 > > On Tue, 2022-03-22 at 07:57 -0400, Matthew Treinish wrote:
 > > > On Tue, Mar 22, 2022 at 11:40:46AM +0000, Stephen Finucane wrote:
 > > > > Hey,
 > > > > 
 > > > > I think it's time we retired os-testr. It is already effectively
 > > > > unmaintained and we made a concerted effort some cycles ago to migrate
 > > > > all projects to stestr. I think it's time we finally closed that out.
 > > > > For any projects still using os-testr, stestr effectively provides a
 > > > > drop-in replacement.
 > > > > 
 > > > > I'll propose patches to do this shortly. Please let me know if anyone
 > > > > has any concerns about this course of action.
 > > > 
 > > > Well the reason we didn't retire it after everything migrated to stestr
 > > > was that the repo contained other utilities for working with subunit
 > > > streams. Primarily, the subunit2html and generate-subunit utilities. I'm
 > > > not sure if they're still being used anywhere, but at least historically
 > > > subunit2html was used to generate the interactive web view of the test
 > > > results and was run at the end of every job. The generate-subunit tool
 > > > was used by at least devstack to have build failures show up in the test
 > > > results stream (this was primarily in support of reporting it to
 > > > subunit2sql which I know has recently shut down so it might not be needed
 > > > anymore).
 > > > 
 > > > I personally don't really have any strong feelings on whether to retire
 > > > the repo or not, but at least the last time we discussed it we kept the
 > > > repo around for those other utilities.
 > > 
 > > i feel like migrating those utilities to there own repo perhaps zuul-jobs
 > > would make more sense if they are in fact still used by zuul to generate
 > > the html report.
 > 
 > Agreed, it would be nice to have at least subunit2html around somewhere.

We can move but we need to check overall benefits of moving them as users has
to use the new location. 

I am not sure why it is considered as not maintained. is it failing in code or gate? In QA, we keep trying
to have them running always. This is not just os-testr but other small stable projects under QA.

I do not have strong opinion on retiring it until we really need to do and it is very costly
to maintain which is not as per the current situation.

-gmann

 > 
 > 
 > -- 
 > Luigi
 > 
 > 
 > 
 >