ikedam commented on Bug JENKINS-23012

Thanks for information.

I tried to reproduce the problem using native processes and I think I could.
I continue the investigation.

How I reproduce:

  • Installed build-timeout-plugin 1.13
  • Create a free style project with "Execute a shell":
    #!/bin/bash
    
    for i in $(seq 300); do
      for j in $(seq 65535); do
        echo ${i} ${j}
      done
    done
    • I tested this on Windows 8, using cygwin for 64 bit.
  • Run a build with and without "Abort the build if it's stuck".
    • "Absolute" Timeout strategy with 30 minutes.


Result:

Condition Duration
Without build-timeout 10 minutes
With build-timeout 12 minutes

and I found that the duration gets 32 minutes if I enabled timestamper-plugin...Amazing.

  • I do have some data captured in a database about those builds. That's data like job-name, build-number, result, build-duration, and interestingly, excerpts from the logs for failed/aborted builds.

If that contains amount of logs, I want to know whether amount of logs affects how much builds get slow.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to