linux-kernel-mentees.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Jay Rajput <jay24rajput@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] Community Bridge Klever Project
Date: Mon, 24 Aug 2020 20:04:54 +0200	[thread overview]
Message-ID: <CAKXUXMzL8WXHbSinWdM01qdQFjnZ30SuBf3Df8uWYH7RMuKHZA@mail.gmail.com> (raw)
In-Reply-To: <CACFir3hREjmsjDoz0t3f3+jenEhqknwNvpdihPsidYY0kMVXPQ@mail.gmail.com>

On Mon, Aug 24, 2020 at 7:53 PM Jay Rajput <jay24rajput@gmail.com> wrote:
>>
>> Okay, all good. The task in this mentorship is to make CodeChecker import
>> the results from coccinelle into the UI.
>>
>> Look at:
>> https://github.com/Ericsson/codechecker/tree/master/tools/report-converter
>>
>> If you can write a first simple report-converter for coccinelle and your
>> prototype shows that you understand what needs to be done, we can devise a
>> plan to make a full-fledged proper implementation with documentation,
>> tests etc. If the plan is solid, I am happy to mentor you through these
>> tasks.
>> If your implementation works, the rough workflow should be:
>>
>> make coccicheck > coccicheck_output
>> report-converter -o coccicheck_report -t coccinelle coccicheck_output
>> CodeChecker server &
>> CodeChecker store ./coccicheck_report -n linux
>>
>> Then, we should see the coccinelle findings nicely presented in the UI.
>>
>> Of course, it might be possible to modify coccinelle, provide parameters
>> to the build target to simplify the parser to be implemented in
>> CodeChecker.
>>
>> If that is not clear, we go back one step in the introduction process of
>> the task.
>
>
> Hello Lukas,
>
> I have looked into the code for report checker and I have devised the workflow and plan for extracting the errors in the document below:
> https://docs.google.com/document/d/1Hbo4REffUS6IN2KzAKB-zAIlvUGO43Rx4adzVnG6HwM/edit?usp=sharing
>
> For the prototype, I would make a basic parser that could extract the error files from the coccinelle output and display it, is that correct? If there is something more please let me know
>

Show that you can program that parser properly in CodeChecker and
share your branch on github to test it.

I am quite sure you did not look at the code yet; your proposal is
just abstract. If you would have looked at the code, you would know
much more specific which data structure is required for CodeChecker to
store it properly in the database.

Lukas
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

      reply	other threads:[~2020-08-24 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACFir3g8CPiN=63am0aLfEU3n9Ft5+ZQ_qJUHQGqqzj96ePHBA@mail.gmail.com>
     [not found] ` <CACFir3jGNRKgcmdAHYDFeLJeO2mXokG5p6yc0WPS0qwCEKNJ6Q@mail.gmail.com>
     [not found]   ` <CAKXUXMx81VxEGEzOX1zhh7ZdGsFGASVMn2Xn9e_MMXyNKjHtRQ@mail.gmail.com>
     [not found]     ` <CACFir3giaV-hyAJ4EoQakznJ271WM9GhXv+tS3S1BvFUoLbz_g@mail.gmail.com>
     [not found]       ` <CAKXUXMzpeUyv8b-KbcR7AAiudi_rU1W+2NyBRtZKHzk15TgrPA@mail.gmail.com>
     [not found]         ` <CACFir3j9PvqJG8Akaa5+3CStwNhfR9JZKvXLuk-GPP9y5DXW0w@mail.gmail.com>
     [not found]           ` <CACFir3ihTHVJjGuEuQ6DZp=QFG+-O8HVzQOK=0nOWsJ-v6C+fw@mail.gmail.com>
     [not found]             ` <CAKXUXMyXmoeFnm2nxLUWYHL=sLCqJAdSZBaCsVPCPLscKztAPA@mail.gmail.com>
     [not found]               ` <CACFir3jCY6kNyzr_7F+r1aRwt9nr78iiPw5b1BtnHfEu_Cxi5w@mail.gmail.com>
2020-08-13 18:01                 ` [Linux-kernel-mentees] Community Bridge Klever Project Lukas Bulwahn
     [not found]     ` <CACFir3jhPhyU1kVkQdzgQ+e4Lq8aqZeT3+dZ6ZsW2b7L9RrBeA@mail.gmail.com>
     [not found]       ` <CAKXUXMxqv_bz+FL1Nckq2FD8gMs9Ymmw3j2MukJKsmgX5ambNA@mail.gmail.com>
     [not found]         ` <CACFir3iwBLcZoS8UqOy4qvtf8gRaQgbvhHWyCREk4XD-ap+BsQ@mail.gmail.com>
     [not found]           ` <CAKXUXMy6waZDaEPWY8g5yyASkoVgCgz6caBqxkZpMMELWOHOcw@mail.gmail.com>
     [not found]             ` <CACFir3jUvTFfoF5CxLw3NSAy+bfLx+9qmaJHMoSpFcC0SPsChw@mail.gmail.com>
     [not found]               ` <CAKXUXMxJdUiR_u6Kh=5SC-i7yc0fo=2JD_syaEPmQwNHCo57ng@mail.gmail.com>
2020-08-18 13:00                 ` Jay Rajput
2020-08-19 18:29                 ` Jay Rajput
2020-08-22 17:27                   ` Lukas Bulwahn
2020-08-24 17:53                     ` Jay Rajput
2020-08-24 18:04                       ` Lukas Bulwahn [this message]

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=CAKXUXMzL8WXHbSinWdM01qdQFjnZ30SuBf3Df8uWYH7RMuKHZA@mail.gmail.com \
    --to=lukas.bulwahn@gmail.com \
    --cc=jay24rajput@gmail.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).