Re: [kernelci-members] Working with the KernelCI project

Dmitry Vyukov
2020-09-30T07:31:54Z

On Tue, Sep 29, 2020 at 7:13 PM Nikolai Kondrashov
<Nikolai.Kondrashov@redhat.com> wrote:
> > 6. We have that tagged Reported-by line that we very much want
> > developers to use in the fixing commit to understand when bugs are
> > fixed.
> > If we detach them from info/reports available in KCIDB, then nobody
> > will use them in commits.
> > How can we pass it to KCIDB? Perhaps it's a useful feature for all
> > reports/test failures? If a bug is reported by Fuego and KCIDB
> > notifications/dashboard will ask to use "Reported-by: fuego", it will
> > give nice credits. We also found use of the hashes in the tag very
> > useful for statistics/tracking purposes. It makes it possible to link
> > failures to fixing commits and understand if a fix (1) exists in
> > general, (2) present in a particular tree, (3) or even if somebody
> > just mailed a proposed fix (useful to identify lost fixes that were
> > never merged, or avoid several people fixing the same bug if you can
> > show that somebody mailed a fix already).
>
> Hmm, yes, that could be very useful indeed, thank you.
>
> We would have to use an ID managed by KCIDB, though. This brings me to the
> question what we're going to use for identifying issues. Perhaps use the
> submitter-supplied ID, similarly to builds and tests right now, under the
> assumption that, at least for the start, issues are not going to be reused
> across CI systems. If that's so, then you would be able to map those IDs back
> to your issues.

If we report a failed test/issue with "id": "syzbot:d195fe572fb15368",
then if the commit includes:
Reported-by: syzbot:d195fe572fb15368
I think it should work for us.