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

The plugin publisher reports no error although the generated xml contains memory violations

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • valgrind-plugin
    • None

      I run the following command as a build step manually (I also tried using the plugin to run valgrind with no effect on the output)

      valgrind --tool=memcheck --leak-check=full --show-reachable=yes --undef-value-errors=yes --track-origins=yes --child-silent-after-fork=no --trace-children=no --error-exitcode=1 --xml=yes --xml-file=./my_report.valgrind ./my_executable;

      my_report.valgrind is generated and it contains couple of errors. But the publisher doesn't seem to pick that up. And when I click on the Valgrind Result link in the my project's home page it tells me no errors

      I've set the Report Pattern field to the expected xml name (i.e. wimatek_ps.valgrind).

      Am I doing something wrong?

      Below are the versions I'm using
      Jenkins version 1.567
      Valgrind plug-in version 0.20
      Valgrind version valgrind-3.10.0.SVN

        1. suggested_publisher_configuration_screenshot.png
          suggested_publisher_configuration_screenshot.png
          22 kB

          [JENKINS-23529] The plugin publisher reports no error although the generated xml contains memory violations

          Mohamed Galal El-Din added a comment -

          I configured the plugin to run valgrind and publish the result, and below was the valgrind related output in the build console:

          [Valgrind] includes files: my_executable
[Valgrind] detected valgrind version (valgrind): 3.10.0
[Valgrind] working dir: /var/lib/jenkins/jobs/my_path
[Valgrind] valgrind exit code: 0
[Valgrind] valgrind standard out: 
[Valgrind] Files to copy:
[Valgrind] Analysing valgrind results; configure Jenkins system log (ValgrindLogger) for details
[Valgrind] Analysing valgrind results
[Valgrind] Ending the valgrind analysis.

          Mohamed Galal El-Din added a comment - I configured the plugin to run valgrind and publish the result, and below was the valgrind related output in the build console: [Valgrind] includes files: my_executable [Valgrind] detected valgrind version (valgrind): 3.10.0 [Valgrind] working dir: / var /lib/jenkins/jobs/my_path [Valgrind] valgrind exit code: 0 [Valgrind] valgrind standard out: [Valgrind] Files to copy: [Valgrind] Analysing valgrind results; configure Jenkins system log (ValgrindLogger) for details [Valgrind] Analysing valgrind results [Valgrind] Ending the valgrind analysis.

          Johannes Ohlemacher added a comment -

          just looked into it, could not reproduce the problem you described.

          What exactly does your Report Pattern look like?
          I noticed that something like './my_report.valgrind' does not work (the plugin finds no reports, hence no reported errors)! Try 'my_report.valgrind' instead!

          Johannes Ohlemacher added a comment - just looked into it, could not reproduce the problem you described. What exactly does your Report Pattern look like? I noticed that something like './my_report.valgrind' does not work (the plugin finds no reports, hence no reported errors)! Try 'my_report.valgrind' instead!

          Mohamed Galal El-Din added a comment -

          Suggested screenshot instead of the one used on the plugin page.

          Mohamed Galal El-Din added a comment - Suggested screenshot instead of the one used on the plugin page.

          Mohamed Galal El-Din added a comment -

          The plugin is fine and it's my fault. I was under the impression that the Report Pattern will be used to search for the report in the output directory specified in the Run configuration. The documentation clearly says these configuration are independent.

          It would be nice if the screenshot of the publisher configuration is changed to reflect that and also match the configuration used in the Runner Options screenshot. I've attached a suggested screenshot.

          This might simplify the publisher configuration a little for new user like me.

          Mohamed Galal El-Din added a comment - The plugin is fine and it's my fault. I was under the impression that the Report Pattern will be used to search for the report in the output directory specified in the Run configuration. The documentation clearly says these configuration are independent. It would be nice if the screenshot of the publisher configuration is changed to reflect that and also match the configuration used in the Runner Options screenshot. I've attached a suggested screenshot. This might simplify the publisher configuration a little for new user like me.

          Mohamed Galal El-Din added a comment -

          It was a misunderstanding on my side partially influenced by the screenshot on the plugin page.

          Mohamed Galal El-Din added a comment - It was a misunderstanding on my side partially influenced by the screenshot on the plugin page.

          Johannes Ohlemacher added a comment -

          FYI: i added a new publisher option to version 0.21: 'fail build on missing reports'
          Enabling this option should help to track down such problems!

          Johannes Ohlemacher added a comment - FYI: i added a new publisher option to version 0.21: 'fail build on missing reports' Enabling this option should help to track down such problems!

            existence Johannes Ohlemacher
            mgalaleldin Mohamed Galal El-Din
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: