QA (public) » openQA Project (public)

I will implement this in JDP instead of OpenQA (it could still be implemented in OpenQA as well).

Looks easy to takeover all bsc/poo, just curious to know any concern to only takeover 1 bsc/poo in current code?

Yeah, no need to takeover comments, but issues/poo are really needed :)

@yosun I am not quite sure if you understood coolo. Every "bug reference" within openQA is also a comment.

Taking over multiple issues is easy and already working: Just do what we already do for very long e.g. within the openSUSE tests, write one comment with a list of references. Take for example https://openqa.opensuse.org/tests/813745#comment-31402 using a proper markdown list with the module and the according ticket reference.

I assume extending the comments on job level to reference multiple issues in multiple failing modules and trying to carry that over to another job with multiple issues in potentially different failing modules would be very complicated and error-prone. I would rather suggest to invest the effort into a different approach to better identify "known failures" and track these not in job comments, e.g. see #39719

I'm fine with taking over the latest comment containing one or multiple issues.

And that already seems to work (see Oliver's example: https://openqa.opensuse.org/tests/813745#comment-31402). So can we consider the issue resolved/rejected then?

@okurz Thanks to notice, I did misunderstood coolo.
But that markdown solution in one comment works for me, what I need it's a solution. Thanks.