• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • warnings-plugin
    • None
    • Jenkins 2.32.3, warnings plugin 4.60

      I have a pipeline job where the warnings are displayed only sometimes. When building a new commit, they are there. Rebuilding that commit shows the warnings, until it doesn't anymore. Rebuilding after that doesn't bring them back in the report (of course they are present in the log). If it should matter, it is with the Erlang parser.

          [JENKINS-42642] Warnings reported intermittently

          Vlad Dumitrescu created issue -

          Ulli Hafner added a comment -

          Please add more details (e.g., screenshots), I don't understand what exactly is the problem. Where are no warnings shown? What messages are in the log?

          Ulli Hafner added a comment - Please add more details (e.g., screenshots), I don't understand what exactly is the problem. Where are no warnings shown? What messages are in the log?
          Ulli Hafner made changes -
          Resolution New: Incomplete [ 4 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Vlad Dumitrescu made changes -
          Attachment New: jenkins_error.png [ 36393 ]

          Vlad Dumitrescu added a comment - - edited

          As you can see, builds 24 to 30 are for the same commit. #27 reports no warnings (not only the graph). The logs for each run are identical (except timestamps and such). The relevant lines are below the image, as well as the excerpt from the Jenkinsfile calling the reporter.

          ===> Compiling erlide_ide
          _build/default/lib/erlide_ide/src/model/erlide_db.erl:24: Warning: type kind() is unused
          _build/default/lib/erlide_ide/src/model/erlide_db.erl:100: Warning: function module_key/1 is unused
          _build/default/lib/erlide_ide/src/model/erlide_db.erl:103: Warning: function module_props/2 is unused
           
          step([$class: 'WarningsPublisher', canComputeNew: false, canResolveRelativePaths: true, canRunOnFailed: true,
          consoleParsers: [[parserName: 'Erlang Compiler (erlc)'], [parserName: 'Maven']],
          excludePattern: '', healthy: '', includePattern: '', messagesPattern: '', unHealthy: ''])
           

          Vlad Dumitrescu added a comment - - edited As you can see, builds 24 to 30 are for the same commit. #27 reports no warnings (not only the graph). The logs for each run are identical (except timestamps and such). The relevant lines are below the image, as well as the excerpt from the Jenkinsfile calling the reporter. ===> Compiling erlide_ide _build/default/lib/erlide_ide/src/model/erlide_db.erl:24: Warning: type kind() is unused _build/default/lib/erlide_ide/src/model/erlide_db.erl:100: Warning: function module_key/1 is unused _build/default/lib/erlide_ide/src/model/erlide_db.erl:103: Warning: function module_props/2 is unused   step([$class: 'WarningsPublisher', canComputeNew: false, canResolveRelativePaths: true, canRunOnFailed: true, consoleParsers: [ [parserName: 'Erlang Compiler (erlc)'] , [parserName: 'Maven'] ], excludePattern: '', healthy: '', includePattern: '', messagesPattern: '', unHealthy: ''])  

          Ulli Hafner added a comment - - edited

          What are the [WARNINGS] messages in the console log for job 27?

          Ulli Hafner added a comment - - edited What are the [WARNINGS] messages in the console log for job 27?

          Do you mean this? It is identical to the other jobs' (except for the reference build for deltas)

          ===> Compiling erlide_ide
          _build/default/lib/erlide_ide/src/model/erlide_db.erl:24: Warning: type kind() is unused
          _build/default/lib/erlide_ide/src/model/erlide_db.erl:100: Warning: function module_key/1 is unused
          _build/default/lib/erlide_ide/src/model/erlide_db.erl:103: Warning: function module_props/2 is unused

          [Pipeline] step
          [WARNINGS] Parsing warnings in console log with parser Erlang Compiler (erlc)
          [WARNINGS] Parsing warnings in console log with parser Maven
          [WARNINGS] Computing warning deltas based on reference build #26
          [Pipeline] step

          Vlad Dumitrescu added a comment - Do you mean this? It is identical to the other jobs' (except for the reference build for deltas) ===> Compiling erlide_ide _build/default/lib/erlide_ide/src/model/erlide_db.erl:24: Warning: type kind() is unused _build/default/lib/erlide_ide/src/model/erlide_db.erl:100: Warning: function module_key/1 is unused _build/default/lib/erlide_ide/src/model/erlide_db.erl:103: Warning: function module_props/2 is unused [Pipeline] step [WARNINGS] Parsing warnings in console log with parser Erlang Compiler (erlc) [WARNINGS] Parsing warnings in console log with parser Maven [WARNINGS] Computing warning deltas based on reference build #26 [Pipeline] step

          Ulli Hafner added a comment -

          Are the messages the same for the other builds? The warnings plugin should report a line that shows the actual number of warnings...

          Maybe this is related to JENKINS-32191. Can you please add a sleep after your erlang build step?

          Ulli Hafner added a comment - Are the messages the same for the other builds? The warnings plugin should report a line that shows the actual number of warnings... Maybe this is related to JENKINS-32191 . Can you please add a sleep after your erlang build step?
          Ulli Hafner made changes -
          Resolution Original: Incomplete [ 4 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          Yep, a sleep seems to fix it, so I guess it's a duplicate of  JENKINS-32191. Thanks!

          Vlad Dumitrescu added a comment - Yep, a sleep seems to fix it, so I guess it's a duplicate of  JENKINS-32191 . Thanks!

            drulli Ulli Hafner
            vladdu Vlad Dumitrescu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: