On Mon, Sep 20, 2021 at 4:24 PM Basil Crow <m...@basilcrow.com> wrote:
> I do not think it is appropriate to imply that a developer caused a > regression […] simply because an operational failure occurred. > That was my best guess based on running `git bisect`: with the parallel class loading, the docs generator failed; without it, the generator worked. As mentioned, we have only speculated on what the real cause of the OOME was—something triggered by parallel class loading, which does not imply a root cause. For example, Jenkins might simply start faster in multiple threads, enabled by parallel class loading, and then do something unrelated to class loading which allocates lots of heap too quickly for GC to keep up. Sounds like the instability in core builds themselves was unrelated, a coincidence? -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr341MSGhzzYaFN0aoMiXoNj8oLkUEjuh_eMdV3xqHKOnA%40mail.gmail.com.
