From: Greg KH <gregkh@linuxfoundation.org>
To: cki-project@redhat.com
Cc: stable@vger.kernel.org
Subject: Re: ❌ FAIL: Test report for 122bb8ac (stable-queue)
Date: Tue, 16 Aug 2022 13:54:38 +0200 [thread overview]
Message-ID: <YvuFfp/wfn4UFYpn@kroah.com> (raw)
In-Reply-To: <92005.122081607111901341@us-mta-567.us.mimecast.lan>
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
next prev parent reply other threads:[~2022-08-16 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 11:11 ❌ FAIL: Test report for 122bb8ac (stable-queue) cki-project
2022-08-16 11:54 ` Greg KH [this message]
2022-08-16 15:36 ` Veronika Kabatova
2022-08-16 15:52 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YvuFfp/wfn4UFYpn@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cki-project@redhat.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox