iirc the number of threads was increased to improve performance. Reducing is fine, but do we understand why it's failing? Perhaps it's finding real issues as a result of the artificial concurrency/load.
Patrick On Fri, Oct 12, 2018 at 7:12 AM Andor Molnar <[email protected]> wrote: > Thanks for the feedback. > I'm running a few tests now: branch-3.5 on 2 threads and trunk on 4 threads > to see what's the impact on the build time. > > Github PR job is hard to configure, because its settings are hard coded > into a shell script in the codebase. I have to open PR for that. > > Andor > > > > On Fri, Oct 12, 2018 at 2:46 PM, Norbert Kalmar < > [email protected]> wrote: > > > +1, running the tests locally with 1 thread always passes (well, I run it > > about 5 times, but still) > > On the other hand, running it on 8 threads yields similarly flaky results > > as Apache runs. (Although it is much faster, but if we have to run 6-8-10 > > times sometimes to get a green run...) > > > > Norbert > > > > On Fri, Oct 12, 2018 at 2:05 PM Enrico Olivelli <[email protected]> > > wrote: > > > > > +1 > > > > > > Enrico > > > > > > Il ven 12 ott 2018, 13:52 Andor Molnar <[email protected]> ha scritto: > > > > > > > Hi, > > > > > > > > What do you think of changing number of threads running unit tests in > > > > Jenkins from current 8 to 4 or even 2? > > > > > > > > Running unit tests inside Cloudera environment on a single thread > shows > > > the > > > > builds much more stable. That would be probably too slow, but maybe > > > running > > > > at least less threads would improve the situation. > > > > > > > > It's getting very annoying that I cannot get a green build on GitHub > > with > > > > only a few retests. > > > > > > > > Regards, > > > > Andor > > > > > > > -- > > > > > > > > > -- Enrico Olivelli > > > > > >
