[Bug 1823429] Re: linux v4.15 ftbfs on a newer host kernel (e.g. hwe)

[Dimitri John Ledkov]

Hi,

I now also see spamming unrelated bugs issue too. That's fine.

Re:message no, the tags are not enough, as there also need to be tasks open
against the right packages. Often the same bug link is used for multiple
kernel flavours affecting different series and fixed at different uploads
so one needs to know package name + version + series.

You can see the current sru template verification text in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700/comments/7
which is more polite and contains more substituted variables with direct
information and links as to what needs testing. I believe it is generated
by the sru-accept script from the ubuntu-archive-tools and is posted upon
publication in the proposed pocket.

There are many ways to drive those scripts, so a full message is generated
when sourcepackage name is passed to it.

https://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/view/head:/sru_workflow.py

I am not sure where the kernel sru messages are generated, is it done with
the sru_workflow tooling using the latest args / messages?

On Fri, 23 Aug 2019, 03:33 Brad Figg, <brad.figg at canonical.com> wrote:

> Dimitri,
>
> A couple of things. First, it appears that a number of bugs are getting
> spammed incorrectly with this for some unknown reason. We are looking into
> why that has happened. Second, this is the same message that we've used for
> years and the message does indicate, via the tags to set, which series is
> to be tested. If the messages are not clear enough we are happy to make
> them more clear.
>
> Brad
>
> On Thu, Aug 22, 2019 at 5:28 PM Dimitri John Ledkov <xnox at ubuntu.com>
> wrote:
>
>> Hi,
>>
>> Kernel bug reports appear to be using non standard SRU notifications.
>>
>> There is never a comment stating the source package name, series, and
>> version requesting verification like it is done on regular SRUs.
>>
>> There is comment as seen below, which makes it impossible to tell what to
>> test.
>>
>> Bug tasks are missing too. If you look at the bug report, you will notice
>> no xenial tasks at all.
>>
>> What am I supposed to test?
>>
>> ---------- Forwarded message ---------
>> From: Ubuntu Kernel Bot <kernel-team-bot at canonical.com>
>> Date: Thu, 22 Aug 2019, 17:29
>> Subject: [Bug 1823429] Re: linux v4.15 ftbfs on a newer host kernel (e.g.
>> hwe)
>> To: <launchpad at surgut.co.uk>
>>
>>
>> This bug is awaiting verification that the kernel in -proposed solves
>> the problem. Please test the kernel and update this bug with the
>> results. If the problem is solved, change the tag 'verification-needed-
>> xenial' to 'verification-done-xenial'. If the problem still exists,
>> change the tag 'verification-needed-xenial' to 'verification-failed-
>> xenial'.
>>
>> If verification is not done by 5 working days from today, this fix will
>> be dropped from the source code, and this bug will be closed.
>>
>> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
>> to enable and use -proposed. Thank you!
>>
>>
>> ** Tags added: verification-needed-xenial
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1831645).
>> https://bugs.launchpad.net/bugs/1823429
>>
>> Title:
>>   linux v4.15 ftbfs on a newer host kernel (e.g. hwe)
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823429/+subscriptions
>> --
>> Ubuntu-release mailing list
>> Ubuntu-release at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
>>
>
>
> --
> Brad Figg brad.figg at canonical.com http://www.canonical.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-release/attachments/20190823/2f0b1837/attachment.html>