Skip to content

Show analysis status per file: successful/outdated/cannot analyze/error #137

Description

@dkrupp

The "Reports in the Current File" view displays the reports for the current file.

Image

However the result list is simply empty if
a) The file was analyzed sucessfully and there are no reports
b) The file was analyzed with failiure and there is no report
c) The file was not found in the compilation database and cannot be analyzed at all

Also if the analyzed file changes, the old outdated results remain in the results list and the user is not notified that the results are outdated.

Requiremets

Show the analysis status per file as main element in this results tree based on CodeChecker parse --status --detailed --e json detailed analysis status feature introduced in CodeChecker 6.27.1 and distinguish the following cases
a) cannot analyze the file
b) analyzed with error
c) analysis outdated
d) analysis successful and up-to date

In case of c) a reanalyze current file button can be placed in the tree for user convenience.
In case of error a link to the "CodeChecker process logs" could be shown so the user sees the output
Image

Activity

  1. added this to the 1.6 milestone on Nov 22, 2023
  2. dkrupp commented on Nov 24, 2023

    @dkrupp
    MemberAuthor

    To proceed with this, CodeChecker parse should give more info about the anlysis state.
    Ericsson/codechecker#4100

  3. dkrupp commented on Nov 24, 2023

    @dkrupp
    MemberAuthor

    Also give warning if the file had analysis failures.

  4. changed the title [-]Warn the user if the file cannot be analyzed (because it is missing from the compilation db)[/-] [+]Warn the user if the file cannot be analyzed (because it is missing from the compilation db) or if the analysis results are outdated[/+] on Jan 10, 2026
  5. changed the title [-]Warn the user if the file cannot be analyzed (because it is missing from the compilation db) or if the analysis results are outdated[/-] [+]Show analysis status per file: successful/outdated/cannot analyze/error[/+] on Jan 10, 2026
  6. dkrupp commented on Jun 10, 2026

    @dkrupp
    MemberAuthor

    Implemented by #163

  7. modified the milestones: 1.6, 1.7.0 on Jun 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

HIGHbugSomething isn't working

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions