QA (public) » openQA Project (public)

Implemented and pushed to my fork.
Now finding out which tests to change and/or extend.

Does t/ui/01-list.t from my suggestions not work?

okurz wrote:

Does t/ui/01-list.t from my suggestions not work?

My approach was to first let CI run all tests and see if I broke something, and go from there.

Looks good. Maybe except for the unexpected difference in line wrapping.

I added a test for an open bugref.
Will add tests for the other cases as well.

Note: Showing comment data was completely disabled in the past due to performance reasons for the running and scheduled tests, according to the comments in the code I found.
So I implement this only for the finished tests.

Note to self:

# Use this list for showing relevant tests with coments, bugrefs and labels
my %ids = qw( 1811909 1 1811550 1 1811761 1 1811897 1 1811912 1 1812121 1 1811554 1 );
@jobs = grep { $ids{ $_->id } } @jobs;
# in loop:
if ($job_id == 1811554) {
    $comment_data{comments} = 2;
}

likely regression #95281

I fixed #95281 by rolling back with a revert PR and deploy that on both o3 and osd. I also created a follow-up #95293

New PR: https://github.com/os-autoinst/openQA/pull/4035

I actually wanted to add this message last week, but didn't see the redmine conflict when I clicked Submit.