zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Enrico Olivelli <eolive...@gmail.com>
Subject Re: Jenkins issues
Date Fri, 04 Jan 2019 08:51:55 GMT
Il ven 4 gen 2019, 09:38 Andor Molnar <andor@apache.org> ha scritto:

> Holy … ! It does kill other test processes!
>
> In test-github-pr.sh:
>
> "### Kill any rogue build processes from the last attempt”
>
> Following a kill command which checks for process IDs of previous runs
> which potentially matches other executions on the same machine.
>
> Is it possible to setup the Jenkins job to prevent multiple executions on
> the same slave?
>

I will check today, IIRC you can limit only the overall number of
concurrent jobs, not per-machine

Enrico

>
> Andor
>
>
>
>
> > On 2019. Jan 3., at 22:49, Enrico Olivelli <eolivelli@gmail.com> wrote:
> >
> > Your ticket has been closed.
> > I think our script won't kill other executions but I need to check.
> > Btw. We can configure the job in order to run at most one execution at a
> > time. Zookeeper test suite is pretty heavy (it does a lot of fsyncs for
> > instance) and we are running test concurrently, so at least putting a
> limit
> > to the job seems reasonable to me
> >
> >
> > Enrico
> >
> > Il gio 3 gen 2019, 13:35 Andor Molnar <andor@apache.org> ha scritto:
> >
> >> Hi team,
> >>
> >> I’m not sure, but it looks like we cannot run 2 concurrent PreCommit
> jobs
> >> on a single Jenkins slave, because both of them get killed soon after
> the
> >> second starts. Additionally all of the recent builds running on H19 for
> >> some reason. I opened an INFRA ticket to track and get help:
> >>
> >> https://issues.apache.org/jira/browse/INFRA-17533 <
> >> https://issues.apache.org/jira/browse/INFRA-17533>
> >>
> >> Regards,
> >> Andor
> >>
> >>
> >> --
> >
> >
> > -- Enrico Olivelli
>
> --


-- Enrico Olivelli

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message