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

File timeout scanning for indication (Build Failure Analyzer Plugin)

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • Build Failure Analyzer 1.19.0
      Jenkins 2.63

      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.

          [JENKINS-44890] File timeout scanning for indication (Build Failure Analyzer Plugin)

          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.

          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.

          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.

          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.

          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.

          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.

          That totally helps, thank you t_westling!

          Marc Neureiter added a comment - That totally helps, thank you t_westling !

          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.

          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.

            t_westling Tomas Westling
            marcodeneu Marc Neureiter
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: