|
||||||||
|
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.
Mocking out getEstimatedDurationCandidates does not prove that this is the issue—you need to show that the problem is actually symlink resolution—but based on thread dumps I have seen, I am optimistic that avoiding the symlink calls should help.
@stephenconnolly and I found this issue while reviewing preliminary results of scalability testing on a test Jenkins instance in EC2 with some thousands of jobs constantly running builds.