• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • valgrind-plugin
    • None

      When I set the working directory and I attempt to build the prohject in Jenkins using the valgrind plugin to run valgrind (valgrind-3.8.1) all I get in the log is:

      [Valgrind] includes files:
      $ valgrind --version
      [Valgrind] detected valgrind version (valgrind): 3.8.1
      [FINDBUGS] Collecting findbugs analysis files...

      If I delete the setting in the working directory and build again I see:

      (I have tried both "BasicStartExitSendOrders*" and "BasicStartExitSendOrdersTest" and get the same result.)

      [Valgrind] includes files: BasicStartExitSendOrdersTest
      $ valgrind --version
      [Valgrind] detected valgrind version (valgrind): 3.8.1
      [Valgrind] working dir: /home/jenkins/workspace/NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender
      [NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender] $ valgrind --tool=memcheck --leak-check=full --show-reachable=no --undef-value-errors=no --track-origins=no --child-silent-after-fork=no --trace-children=no --xml=yes --xml-file=/home/jenkins/workspace/NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender/sender/reports/valgrind/BasicStartExitSendOrdersTest.%p.xml /home/jenkins/workspace/NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender/sender/build/cpp/src/Test/BasicStartExitSendOrdersTest

      [Valgrind] valgrind exit code: 201
      [Valgrind] valgrind standard out:
      ERROR: Unable to initialize logger - configuration file is not specified. Please set environment variable LOG4CXX_CONFIG_FILE
      Running 8 test cases...
      unknown location(0): fatal error in "SenderCtor": std::runtime_error: Required parameter 'MSG_SIZE' has no specified value.
      unknown location(0): fatal error in "SenderInit": std::runtime_error: Required parameter 'MSG_SIZE' has no specified value.
      unknown location(0): fatal error in "SenderInitWithMITSim": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file.
      unknown location(0): fatal error in "SenderInitWithMITSimAndRunner": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file.
      unknown location(0): fatal error in "SenderProcessANewOrderMsg": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file.
      unknown location(0): fatal error in "SenderProcessACancelOrderMsg": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file.
      unknown location(0): fatal error in "SenderProcessAReplaceOrderMsg": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file.
      unknown location(0): fatal error in "SenderSoakTestNewOrderParallel": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file.
      [Valgrind] valgrind error out:
      log4cxx: No appender could be found for logger (com.nomura.nxtdirect.nxt-direct-user.NxtDirectSender).
      log4cxx: Please initialize the log4cxx system properly.

          • 8 failures detected in test suite "Master Test Suite"
            Build step 'Run Valgrind' marked build as failure
            [FINDBUGS] Skipping publisher since build result is FAILURE

      Also please clarify the help text on the "Executable Include Pattern" edit box to indicate if it is relative to the entry in the "Working Directory" edit box. Thank you.

          [JENKINS-24971] valgrind not run if working directory set.

          I am not sure why it was that way, but the patterns being relative to the working directory made absolutely no sense and i considered that a bug.

          With version 0.23 patterns are now always relative to workspace.

          Johannes Ohlemacher added a comment - I am not sure why it was that way, but the patterns being relative to the working directory made absolutely no sense and i considered that a bug. With version 0.23 patterns are now always relative to workspace.

          J McG added a comment -

          Thanks for the advice. I note that the download page for the plugin lists 0.22 as the latest version:

          https://wiki.jenkins-ci.org/display/JENKINS/Valgrind+Plugin

          I quote:

          "Latest Release 0.22 (archives)
          Latest Release Date Sep 16, 2014
          Required Core 1.424"

          We use Jenkins v1.577. I also note that the changelog lists v0.24, which appears to be unavailable, and I can't find a link to it anywhere. Please can you advise?

          J McG added a comment - Thanks for the advice. I note that the download page for the plugin lists 0.22 as the latest version: https://wiki.jenkins-ci.org/display/JENKINS/Valgrind+Plugin I quote: "Latest Release 0.22 (archives) Latest Release Date Sep 16, 2014 Required Core 1.424" We use Jenkins v1.577. I also note that the changelog lists v0.24, which appears to be unavailable, and I can't find a link to it anywhere. Please can you advise?

          The release of the original version 0.23 failed and i did not notice that immediately.
          I did a new release (0.24) a couple of hours ago and you can download the plugin manually from here:

          http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/valgrind/0.24/

          It will take up to 12 hours until its visible in jenkins update center and on the website.
          That delay is very unfortunate, but it's the way the jenkins infrastructure works ;(

          Johannes Ohlemacher added a comment - The release of the original version 0.23 failed and i did not notice that immediately. I did a new release (0.24) a couple of hours ago and you can download the plugin manually from here: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/valgrind/0.24/ It will take up to 12 hours until its visible in jenkins update center and on the website. That delay is very unfortunate, but it's the way the jenkins infrastructure works ;(

          J McG added a comment - - edited

          (BTW: I think your considering the path relative to the working dir as a bug is what I thought too. Relative to the workspace like most of the other settings in Jenkins seems much more sensible! Thank you very much for your incredibly prompt, clear and helpful response! Thanks again.

          J McG added a comment - - edited (BTW: I think your considering the path relative to the working dir as a bug is what I thought too. Relative to the workspace like most of the other settings in Jenkins seems much more sensible! Thank you very much for your incredibly prompt, clear and helpful response! Thanks again.

            existence Johannes Ohlemacher
            jmmcg1 J McG
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: