Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-71571

GCC C Warnings results are inconsitent for multi-configuration projects

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • warnings-ng-plugin
    • Jenkins 2.401.2 + Warnings Next Generation Plugin 10.2.0

      The number of warnings deviates significantly from build to build even if no source code changes made. Here is the history of last 8 rebuilds (rebuild last).

       

          [JENKINS-71571] GCC C Warnings results are inconsitent for multi-configuration projects

          Ulli Hafner added a comment -

          When you do not provide details (parsed log content, log output of plugin), I cannot help.

          Ulli Hafner added a comment - When you do not provide details (parsed log content, log output of plugin), I cannot help.

          Aleksandrs Gumenuks added a comment - - edited

          When you do not provide details (parsed log content, log output of plugin), I cannot help. 

          I am happy to provide everything you need to solve this issue. Tell me please what kind of logs exactly do you need for the analysis?

          Where can I find this logs?

          Aleksandrs Gumenuks added a comment - - edited When you do not provide details (parsed log content, log output of plugin), I cannot help.  I am happy to provide everything you need to solve this issue. Tell me please what kind of logs exactly do you need for the analysis? Where can I find this logs?

          build_15_16.zip

          Here are the two sequential builds 15 and 16.

          The source code base is the same: dc8624b23ed5a3e5b4b388564e35fc9e70433ca5;

          However the number of issues detected is different.

          Build 15 Build 16
           > git checkout -f dc8624b23ed5a3e5b4b388564e35fc9e70433ca5 # timeout=10​  > git checkout -f dc8624b23ed5a3e5b4b388564e35fc9e70433ca5 # timeout=10
          [Static Analysis] Using reference build '11-PMP_ng-master-Build #14' to compute new, fixed, and outstanding issues
          [Static Analysis] Issues delta (vs. reference build): outstanding: 110, new: 4, fixed: 2
          [Static Analysis] Using reference build '11-PMP_ng-master-Build #15' to compute new, fixed, and outstanding issues
          [Static Analysis] Issues delta (vs. reference build): outstanding: 110, new: 2, fixed: 4

          Aleksandrs Gumenuks added a comment - build_15_16.zip Here are the two sequential builds 15 and 16. The source code base is the same: dc8624b23ed5a3e5b4b388564e35fc9e70433ca5; However the number of issues detected is different. Build 15 Build 16  > git checkout -f dc8624b23ed5a3e5b4b388564e35fc9e70433ca5 # timeout=10​  > git checkout -f dc8624b23ed5a3e5b4b388564e35fc9e70433ca5 # timeout=10 [Static Analysis] Using reference build '11-PMP_ng-master-Build #14' to compute new, fixed, and outstanding issues [Static Analysis] Issues delta (vs. reference build): outstanding: 110, new: 4, fixed: 2 [Static Analysis] Using reference build '11-PMP_ng-master-Build #15' to compute new, fixed, and outstanding issues [Static Analysis] Issues delta (vs. reference build): outstanding: 110, new: 2, fixed: 4

          Please allow me to reopen the issue since have just added some logs there.

          Aleksandrs Gumenuks added a comment - Please allow me to reopen the issue since have just added some logs there.

          Here some more extensive logs build_15_16_with_more_logs.zip

          Aleksandrs Gumenuks added a comment - Here some more extensive logs build_15_16_with_more_logs.zip

          Ulli Hafner added a comment - - edited

          Is it only a difference in the new warnings? This may be related to the fingerprinting algorithm, see JENKINS-6675 and JENKINS-5935 for details.

          Ulli Hafner added a comment - - edited Is it only a difference in the new warnings? This may be related to the fingerprinting algorithm, see JENKINS-6675 and JENKINS-5935 for details.

          Is it only a difference in the new warnings? This may be related to the fingerprinting algorithm, see JENKINS-6675 and JENKINS-5935 for details.

          I don't think they are directly related to each other. The total number of issues different as well 114@15 and 112@16.

          Build 15 Build 16
          11:52:10 [Static Analysis] Issues delta (vs. reference build): outstanding: 110, new: 4, fixed: 2
          11:52:10 [Static Analysis] No quality gates have been set - skipping
          11:52:10 [Static Analysis] Health report is disabled - skipping
          11:52:10 [Static Analysis] Created analysis result for 114 issues (found 4 new issues, fixed 2 issues)
          11:52:10 [Static Analysis] Attaching ResultAction with ID 'gcc' to build '11-PMP_ng-master-Build #15'.
          11:55:34 [Static Analysis] Issues delta (vs. reference build): outstanding: 110, new: 2, fixed: 4
          11:55:34 [Static Analysis] No quality gates have been set - skipping
          11:55:34 [Static Analysis] Health report is disabled - skipping
          11:55:34 [Static Analysis] Created analysis result for 112 issues (found 2 new issues, fixed 4 issues)
          11:55:34 [Static Analysis] Attaching ResultAction with ID 'gcc' to build '11-PMP_ng-master-Build #16'.

          Aleksandrs Gumenuks added a comment - Is it only a difference in the new warnings? This may be related to the fingerprinting algorithm, see JENKINS-6675 and JENKINS-5935 for details. I don't think they are directly related to each other. The total number of issues different as well 114@15 and 112@16. Build 15 Build 16 11:52:10 [Static Analysis] Issues delta (vs. reference build): outstanding: 110, new: 4, fixed: 2 11:52:10 [Static Analysis] No quality gates have been set - skipping 11:52:10 [Static Analysis] Health report is disabled - skipping 11:52:10 [Static Analysis] Created analysis result for 114 issues (found 4 new issues, fixed 2 issues) 11:52:10 [Static Analysis] Attaching ResultAction with ID 'gcc' to build '11-PMP_ng-master-Build #15'. 11:55:34 [Static Analysis] Issues delta (vs. reference build): outstanding: 110, new: 2, fixed: 4 11:55:34 [Static Analysis] No quality gates have been set - skipping 11:55:34 [Static Analysis] Health report is disabled - skipping 11:55:34 [Static Analysis] Created analysis result for 112 issues (found 2 new issues, fixed 4 issues) 11:55:34 [Static Analysis] Attaching ResultAction with ID 'gcc' to build '11-PMP_ng-master-Build #16'.

          The error happens with multi-configuration type project.
          The odd thing about it is, that the number of issues for each single configuration stays the same across the builds.
          The total number of issues of aggregated results only (of all build configuration) is inconsistent.

          Aleksandrs Gumenuks added a comment - The error happens with multi-configuration type project. The odd thing about it is, that the number of issues for each single configuration stays the same across the builds. The total number of issues of aggregated results only (of all build configuration) is inconsistent.

            Unassigned Unassigned
            reanimator Aleksandrs Gumenuks
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: