On Fri, Jun 5, 2020 at 1:24 PM Jesse Glick <[email protected]> wrote: > The next step would be PRs to infrastructure repositories.
I agree. Unfortunately I have spent too much time on this issue already and cannot volunteer to become an infrastructure developer at present. > 256Mb seems low for a Surefire JVM—this needs to run Jenkins and all > plugins plus whatever your test code is doing. I agree, which is why I said "I worked around the problem" rather than "I solved the problem." Changing the JVM settings for Surefire and the agent launched by my tests was easy because both those JVMs were completely within my control. I agree that a long-term solution would involve setting -Xmx and -Xms on all agent and Maven JVMs as well as possibly increasing the EC2 instance size for these nodes. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrjW2aA74pqoFMhca%2BD0YqL%3DWvNe46g7G1aM3Bmx5LrWQ%40mail.gmail.com.
