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

error resolving relative path - warnings plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • warnings-plugin
    • None
    • Linux 3.2.0-4-686-pae #1 SMP Debian 3.2.46-1+deb7u1 i686 GNU/Linux
      Jenkins 1.509.4
      Warnings plugin 4.35

      When I try to acces the file of the reported GCC4 warning, I got this error:

      01 Copying the source file '../Code/Monitoring/FctMonitPatientTrigIY.cpp' from the workspace to the build folder '/opt/sdb1/jenkins/jobs/Vendome_ventilator/builds/2013-10-21_15-22-32/workspace-files/994b1dd2.tmp' on the Jenkins master failed.
      02 Seems that the path is relative, however an absolute path is required when copying the sources.
      03 Is the file 'FctMonitPatientTrigIY.cpp' contained more than once in your workspace?
      04 Is the file '../Code/Monitoring/FctMonitPatientTrigIY.cpp' a valid filename?

      The file is unique in the workspace.
      here is the output of "find . | grep FctMonitPatientTrigIY.cpp" (in the workspace folder)
      ./Code/Monitoring/FctMonitPatientTrigIY.cpp
      ./build/CMakeFiles/ventilator.dir/Code/Monitoring/FctMonitPatientTrigIY.cpp.o.d
      ./build/CMakeFiles/ventilator.dir/Code/Monitoring/FctMonitPatientTrigIY.cpp.o

      The automatic relative path option is checked in the project configuration.

      Am I missing something?

          [JENKINS-20150] error resolving relative path - warnings plugin

          Ulli Hafner added a comment -

          Are you using make? Then there is another parser that has a better detection of absolute paths...

          Is the file readable by the Jenkins user?

          Ulli Hafner added a comment - Are you using make? Then there is another parser that has a better detection of absolute paths... Is the file readable by the Jenkins user?

          Philippe Leduc added a comment -

          The file is readable by the jenkins user (I can open it in the workspace view). I am using cmake+ninja right now, but I can use cmake+make on the server side. Is the parser you're speaking about "GNU make + GNU compiler"?

          Philippe Leduc added a comment - The file is readable by the jenkins user (I can open it in the workspace view). I am using cmake+ninja right now, but I can use cmake+make on the server side. Is the parser you're speaking about "GNU make + GNU compiler"?

          Ulli Hafner added a comment -

          Yes this is the other parser, it uses make messages of the form

           
make[1]: Entering directory `/dir1/dir2'

          to identify the absolute path. Maybe it is already working in your case...

          Is your build on the master or slave? Are there any logging messages of my plug-in in Jenkins log?

          Ulli Hafner added a comment - Yes this is the other parser, it uses make messages of the form make[1]: Entering directory `/dir1/dir2' to identify the absolute path. Maybe it is already working in your case... Is your build on the master or slave? Are there any logging messages of my plug-in in Jenkins log?

          Philippe Leduc added a comment - - edited

          The build is on the master. I tried the parser "GNU make + GNU compiler" and it is working with it. I tried again the GCC4 parser to check the plugin log but now it is working... An old artefact/config of the plugin could be responsible of this behavior, artefact which was detroyed when changing the parser?

          Philippe Leduc added a comment - - edited The build is on the master. I tried the parser "GNU make + GNU compiler" and it is working with it. I tried again the GCC4 parser to check the plugin log but now it is working... An old artefact/config of the plugin could be responsible of this behavior, artefact which was detroyed when changing the parser?

          Ulli Hafner added a comment -

          I don't know what caused the problem in the first place. I close this issue, if it occurs again, please reopen.

          Ulli Hafner added a comment - I don't know what caused the problem in the first place. I close this issue, if it occurs again, please reopen.

          Philippe Leduc added a comment -

          OK

          Philippe Leduc added a comment - OK

            drulli Ulli Hafner
            siviuze Philippe Leduc
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: