❌ FAIL: Test report for 122bb8ac (stable-queue)

❌ FAIL: Test report for 122bb8ac (stable-queue)

[cki-project]

Hi, we tested your kernel and here are the results:

    Overall result: FAILED
             Merge: OK
           Compile: FAILED


You can find all the details about the test run at
    https://datawarehouse.cki-project.org/kcidb/checkouts/41055

One or more kernel builds failed:
    Unrecognized or new issues:
          x86_64 - https://datawarehouse.cki-project.org/kcidb/builds/218267


If you find a failure unrelated to your changes, please tag it at https://datawarehouse.cki-project.org .
This will prevent the failures from being incorrectly reported in the future.
If you don't have permissions to tag an issue, you can contact the CKI team or
test maintainers.

Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.

        ,-.   ,-.
       ( C ) ( K )  Continuous
        `-',-.`-'   Kernel
          ( I )     Integration
           `-'
______________________________________________________________________________

Re: ❌ FAIL: Test report for 122bb8ac (stable-queue)

[Greg KH]

On Tue, Aug 16, 2022 at 11:11:18AM -0000, cki-project@redhat.com wrote:
> Hi, we tested your kernel and here are the results:
> 
>     Overall result: FAILED
>              Merge: OK
>            Compile: FAILED
> 
> 
> You can find all the details about the test run at
>     https://datawarehouse.cki-project.org/kcidb/checkouts/41055
> 
> One or more kernel builds failed:
>     Unrecognized or new issues:
>           x86_64 - https://datawarehouse.cki-project.org/kcidb/builds/218267

Am I going to be forced to click through to find out the problems with
all of these reports?  Why not provide the error log?

The error log isn't at that link, where are we supposed to find it to
figure out what went wrong?

> If you find a failure unrelated to your changes, please tag it at https://datawarehouse.cki-project.org .
> This will prevent the failures from being incorrectly reported in the future.
> If you don't have permissions to tag an issue, you can contact the CKI team or
> test maintainers.
> 
> Please reply to this email if you have any questions about the tests that we
> ran or if you have any suggestions on how to make future tests more effective.
> 
>         ,-.   ,-.
>        ( C ) ( K )  Continuous
>         `-',-.`-'   Kernel
>           ( I )     Integration
>            `-'
> ______________________________________________________________________________
> 

I have no idea what the subject line means, sorry.  A random git commit
id with no context isn't helpful, what are we to do with that?

thanks,

greg k-h

Re: ❌ FAIL: Test report for 122bb8ac (stable-queue)

[Veronika Kabatova]

On Tue, Aug 16, 2022 at 2:05 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Aug 16, 2022 at 11:11:18AM -0000, cki-project@redhat.com wrote:
> > Hi, we tested your kernel and here are the results:
> >
> >     Overall result: FAILED
> >              Merge: OK
> >            Compile: FAILED
> >
> >
> > You can find all the details about the test run at
> >     https://datawarehouse.cki-project.org/kcidb/checkouts/41055
> >
> > One or more kernel builds failed:
> >     Unrecognized or new issues:
> >           x86_64 - https://datawarehouse.cki-project.org/kcidb/builds/218267
>

Hi Greg,

we fixed the issue that caused the lack of notifications for build failures
(hence me sending the email manually yesterday), and that in turn
caused some super old emails from May to go out. That was less than
expected, and we're sorry about that.

> Am I going to be forced to click through to find out the problems with
> all of these reports?  Why not provide the error log?
>
> The error log isn't at that link, where are we supposed to find it to
> figure out what went wrong?
>

The logs would normally be available, but as a consequence of the
old emails going out, they were already deleted.

We're also working on a reporting mode that would add the failure
log links into the email directly, and for build failures, embed the
traces in the email body too. Would these two provide a suitable
solution for you?

> > If you find a failure unrelated to your changes, please tag it at https://datawarehouse.cki-project.org .
> > This will prevent the failures from being incorrectly reported in the future.
> > If you don't have permissions to tag an issue, you can contact the CKI team or
> > test maintainers.
> >
> > Please reply to this email if you have any questions about the tests that we
> > ran or if you have any suggestions on how to make future tests more effective.
> >
> >         ,-.   ,-.
> >        ( C ) ( K )  Continuous
> >         `-',-.`-'   Kernel
> >           ( I )     Integration
> >            `-'
> > ______________________________________________________________________________
> >
>
> I have no idea what the subject line means, sorry.  A random git commit
> id with no context isn't helpful, what are we to do with that?

Would it be more useful to provide a branch name in the subject as well,
and a commit description in the body? Or something completely different?


Thank you for the feedback!
Veronika

>
> thanks,
>
> greg k-h
>

Re: ❌ FAIL: Test report for 122bb8ac (stable-queue)

[Greg KH]

On Tue, Aug 16, 2022 at 05:36:39PM +0200, Veronika Kabatova wrote:
> On Tue, Aug 16, 2022 at 2:05 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Aug 16, 2022 at 11:11:18AM -0000, cki-project@redhat.com wrote:
> > > Hi, we tested your kernel and here are the results:
> > >
> > >     Overall result: FAILED
> > >              Merge: OK
> > >            Compile: FAILED
> > >
> > >
> > > You can find all the details about the test run at
> > >     https://datawarehouse.cki-project.org/kcidb/checkouts/41055
> > >
> > > One or more kernel builds failed:
> > >     Unrecognized or new issues:
> > >           x86_64 - https://datawarehouse.cki-project.org/kcidb/builds/218267
> >
> 
> Hi Greg,
> 
> we fixed the issue that caused the lack of notifications for build failures
> (hence me sending the email manually yesterday), and that in turn
> caused some super old emails from May to go out. That was less than
> expected, and we're sorry about that.
> 
> > Am I going to be forced to click through to find out the problems with
> > all of these reports?  Why not provide the error log?
> >
> > The error log isn't at that link, where are we supposed to find it to
> > figure out what went wrong?
> >
> 
> The logs would normally be available, but as a consequence of the
> old emails going out, they were already deleted.
> 
> We're also working on a reporting mode that would add the failure
> log links into the email directly, and for build failures, embed the
> traces in the email body too. Would these two provide a suitable
> solution for you?

That's a good start, yes.

> > > If you find a failure unrelated to your changes, please tag it at https://datawarehouse.cki-project.org .
> > > This will prevent the failures from being incorrectly reported in the future.
> > > If you don't have permissions to tag an issue, you can contact the CKI team or
> > > test maintainers.
> > >
> > > Please reply to this email if you have any questions about the tests that we
> > > ran or if you have any suggestions on how to make future tests more effective.
> > >
> > >         ,-.   ,-.
> > >        ( C ) ( K )  Continuous
> > >         `-',-.`-'   Kernel
> > >           ( I )     Integration
> > >            `-'
> > > ______________________________________________________________________________
> > >
> >
> > I have no idea what the subject line means, sorry.  A random git commit
> > id with no context isn't helpful, what are we to do with that?
> 
> Would it be more useful to provide a branch name in the subject as well,
> and a commit description in the body? Or something completely different?

Think about what you would want to see in an email to try to figure out
what it is trying to say.  Make it obvious what the email is about and
referencing and what needs to be done about it.

thanks,

greg k-h