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

File timeout scanning for indication (Build Failure Analyzer Plugin)

    Details

    • Similar Issues:

      Description

      When using a multiline build log indication I get the following error in the Jenkins logs:

      File timeout scanning for indication '.*UnitTest FAILED.*' for file log
      

      I think there is a means of changing the timeout needed.

      There is no workaround for the problem (thus major).

      There has already been a comment about this problem here but there are no responses so far.

        Attachments

          Activity

          Hide
          t_westling Tomas Westling added a comment -

          Do you mean to use a multiline regex for this? If so, you need to change the way you write your regular expression.

          From the documentation of multiline indication:

          Note that you should not specify "." within your multi-line pattern unless you actually want to match every character. ".*FOO." will match the entire build log, assuming it contains "FOO" somewhere.

          Show
          t_westling Tomas Westling added a comment - Do you mean to use a multiline regex for this? If so, you need to change the way you write your regular expression. From the documentation of multiline indication: Note that you should not specify ". " within your multi-line pattern unless you actually want to match every character. ".*FOO. " will match the entire build log, assuming it contains "FOO" somewhere.
          Hide
          marcodeneu Marc Neureiter added a comment -

          OK but what can you do otherwise to get the wanted behaviour?

          I want to scan for a text in a line but include multiple lines in the reporting.

          Show
          marcodeneu Marc Neureiter added a comment - OK but what can you do otherwise to get the wanted behaviour? I want to scan for a text in a line but include multiple lines in the reporting.
          Hide
          t_westling Tomas Westling added a comment -

          It looks like you are just looking for UnitTest FAILED anywhere in the log.

          Can UnitTest be on one line and FAILED on another, or are they always directly in sequence on one line?

          If they are on one line, use a BuildLogIndication instead. 

          You can't end your multiline with .* because then it will match the remainder of the log as part of the failure.

          You need to know some text which will finish up your uniquely identifiable error text and then write your expression like:

          UnitTest FAILED\s+ending text

          Without any .* in the start or end.

          Show
          t_westling Tomas Westling added a comment - It looks like you are just looking for UnitTest FAILED anywhere in the log. Can UnitTest be on one line and FAILED on another, or are they always directly in sequence on one line? If they are on one line, use a BuildLogIndication instead.  You can't end your multiline with .* because then it will match the remainder of the log as part of the failure. You need to know some text which will finish up your uniquely identifiable error text and then write your expression like: UnitTest FAILED\s+ending text Without any .* in the start or end.
          Hide
          marcodeneu Marc Neureiter added a comment -

          That totally helps, thank you Tomas Westling!

          Show
          marcodeneu Marc Neureiter added a comment - That totally helps, thank you Tomas Westling !
          Hide
          jiangty_addepar Damien Jiang added a comment -

          Hello,

          Sorry to bump an old issue, but we've been running into issues with single-line indications timing out due to our test log files being too long. Thus, I'd like to re-request the ability to configure the timeout length.

          Show
          jiangty_addepar Damien Jiang added a comment - Hello, Sorry to bump an old issue, but we've been running into issues with  single-line indications timing out due to our test log files being too long. Thus, I'd like to re-request the ability to configure the timeout length.

            People

            • Assignee:
              t_westling Tomas Westling
              Reporter:
              marcodeneu Marc Neureiter
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: