No reason. One job always took 1 hour. You do not have to. We are working on a release. If you commit anything to master I can start from the begin. After the release I will use parallel execution but I could not because Gavin from our INFRA team installed latest Pipeline Advanced Utilities few hour ago. There I needed lock() and zip(). Why lock? Because failsafe-plugin has 4 integration tests and they bind to port 8083. If I run them in parallel, one cannot bind. I could find random port via helper-plugin but this was not guarantee either.
On Sun, Feb 18, 2018 at 3:18 PM, Karl Heinz Marbaise <[email protected]> wrote: > Hi Tibor, > > On 18/02/18 15:13, Tibor Digana wrote: > >> no, no >> Please do not do it! >> > > I would have at least waited for a feedback before I kill a Job ;-)... > > > We are waiting for them. >> They are expected to run 12 hours. >> > > Wow that long..I wasn't aware of that... > > You can compute it: >> 1 hour each run configuration. >> Number of configuration is 3 Maven config * 4 JDKs. >> > > > >> I tried to run them in parallel but they appeared several in one executor. >> Maybe later as parallel but now before release it is not safe. We will >> rather wait longer. >> > > Of course not...But I think we should take a deeper look at them and see > if we can get them faster ...after the release... > > > > Kind regards > Karl Heinz Marbaise > > >> On Sun, Feb 18, 2018 at 2:56 PM, Karl Heinz Marbaise <[email protected]> >> wrote: >> >> Hi, >>> >>> On 18/02/18 14:51, Karl Heinz Marbaise wrote: >>> >>> Hi, >>>> >>>> it seemed to me that there are Surefire Jobs stuck ..for 10 hours or >>>> more... >>>> >>>> I would like to abort them ? >>>> >>>> >>> Seemed to be gone already... >>> >>> >>> Kind regards >>> Karl Heinz Marbaise >>> >>> >>>> Kind regards >>>> Karl Heinz Marbaise >>>> >>>
