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

Gcc parser does not resolve absolute paths

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • analysis-model
    • None
    • beta8 (warnings-ng), beta17 (analysis-model-api)

      There are a number of things you can filter from reporting warnings on:

      • excludeCategory
      • pattern
        • Type: String
      • excludeFile
      • pattern
        • Type: String
      • excludeModule
      • pattern
        • Type: String
      • excludePackage
      • pattern
        • Type: String
      • excludeType
      • pattern
        • Type: String

      None of those appears to allow you to just specify a path/directory under which everything should be filtered, for the gcc4 format for example.

      I tried to use an Ant-style directory/*** but that was rejected as having one too many {}'s. I'm not sure that Module or Package will match an arbitrary path either though.

      It seems that this plugin is missing that ability.

        1. consoleText.txt
          5.55 MB

          [JENKINS-54035] Gcc parser does not resolve absolute paths

          Ulli Hafner added a comment -

          https://issues.jenkins-ci.org/browse/JENKINS-54027?focusedCommentId=353188&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-353188

          Seems that the file topology.c is reported with a relative path. This depends on JENKINS-14064.

          Ulli Hafner added a comment - https://issues.jenkins-ci.org/browse/JENKINS-54027?focusedCommentId=353188&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-353188 Seems that the file topology.c is reported with a relative path. This depends on JENKINS-14064 .

          Brian J Murrell added a comment -

          Are you asserting that JENKINS-14064 is why I cannot seem to exclude and entire directory's worth of files/warnings?

          That issue seems quite old.  Is it ever going to be resolved?  Or is there any other kind of workaround I can use?

          I don't think I am doing anything special/different.  Why isn't this affecting everyone using make and gcc?

          Brian J Murrell added a comment - Are you asserting that  JENKINS-14064 is why I cannot seem to exclude and entire directory's worth of files/warnings? That issue seems quite old.  Is it ever going to be resolved?  Or is there any other kind of workaround I can use? I don't think I am doing anything special/different.  Why isn't this affecting everyone using make and gcc ?

          Ulli Hafner added a comment - - edited

          Sorry, maybe I did not understand correctly. I thought the filter is now working as no file that contains build.external is in the report anymore. So this part of the problem is solved.

          The remaining problem is: some files do not have an absolute path attached. This is something that needs to be checked (different issue but still an issue!). Why does your build produce a warning log that does not resolve all absolute filenames. This has been implemented for GCC and Make and should be pulled up for all make based parsers (JENKINS-14064).

          In order to investigate that in more detail I need to analyze an actual GCC project (see your comment). I won't have time to start to work on this issue in the next time, first of all the 1.0 release needs to be finished.

          Ulli Hafner added a comment - - edited Sorry, maybe I did not understand correctly. I thought the filter is now working as no file that contains build.external is in the report anymore. So this part of the problem is solved. The remaining problem is: some files do not have an absolute path attached. This is something that needs to be checked (different issue but still an issue!). Why does your build produce a warning log that does not resolve all absolute filenames. This has been implemented for GCC and Make and should be pulled up for all make based parsers ( JENKINS-14064 ). In order to investigate that in more detail I need to analyze an actual GCC project (see your comment ). I won't have time to start to work on this issue in the next time, first of all the 1.0 release needs to be finished.

          Ulli Hafner added a comment -

          Can I change the description so that it describes the missing absolute paths issue?

          Ulli Hafner added a comment - Can I change the description so that it describes the missing absolute paths issue?

          Brian J Murrell added a comment -

          Ahhh.  So yes, maybe it is working now.  I was just seeing the same approximate (~700) number of files being identified and thinking it was the filtering.

          Why does your build produce a warning log that does not resolve all absolute filenames

          This I am not sure of. Our project is building a number of other projects/software packages under it's build, but those should pretty much all be standard Autotools/Make/GCC based projects.

          Can I change the description so that it describes the missing absolute paths issue?

          Absolutely. Whatever you need to help organise this and get it resolved.

          Brian J Murrell added a comment - Ahhh.  So yes, maybe it is working now.  I was just seeing the same approximate (~700) number of files being identified and thinking it was the filtering. Why does your build produce a warning log that does not resolve all absolute filenames This I am not sure of. Our project is building a number of other projects/software packages under it's build, but those should pretty much all be standard Autotools/Make/GCC based projects. Can I change the description so that it describes the missing absolute paths issue? Absolutely. Whatever you need to help organise this and get it resolved.

          Ulli Hafner added a comment -

          If it is possible, please also attach one of your console log files, then I just can see if I can fix it without setting up a C project. (Or send it via mail if it contains sensible data.)

          Ulli Hafner added a comment - If it is possible, please also attach one of your console log files, then I just can see if I can fix it without setting up a C project. (Or send it via mail if it contains sensible data.)

          Brian J Murrell added a comment -

          Build console log consoleText.txt has been attached.

          Much thanks!

          Brian J Murrell added a comment - Build console log  consoleText.txt has been attached. Much thanks!

          Brian J Murrell added a comment -

          Was the console log I attached helpful?

          Brian J Murrell added a comment - Was the console log I attached helpful?

          Brian J Murrell added a comment -

          Ping?

          Brian J Murrell added a comment - Ping?

          Ulli Hafner added a comment -

          Sorry for the delay... Yes the log file is helpful, I can use it (or a snippet) to create a test case to fix the resolving of the names.

          I'm still struggling with the 1.0 release so please be patient, I did not forget your issue. Just a lot of other things to do.

          Ulli Hafner added a comment - Sorry for the delay... Yes the log file is helpful, I can use it (or a snippet) to create a test case to fix the resolving of the names. I'm still struggling with the 1.0 release so please be patient, I did not forget your issue. Just a lot of other things to do.

            drulli Ulli Hafner
            brianjmurrell Brian J Murrell
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: