From dev-return-76948-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Fri Jan 4 09:38:20 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B43E9180660 for ; Fri, 4 Jan 2019 09:38:19 +0100 (CET) Received: (qmail 17614 invoked by uid 500); 4 Jan 2019 08:38:18 -0000 Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list dev@zookeeper.apache.org Received: (qmail 17603 invoked by uid 99); 4 Jan 2019 08:38:18 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2019 08:38:18 +0000 Received: from [172.30.65.74] (unknown [185.63.45.212]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 622E221E6 for ; Fri, 4 Jan 2019 08:38:17 +0000 (UTC) From: Andor Molnar Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: Jenkins issues Date: Fri, 4 Jan 2019 09:38:03 +0100 References: <23A32DE9-BD9A-490D-BF48-1794B13A3106@apache.org> To: DevZooKeeper In-Reply-To: Message-Id: <841C1D3C-D1FB-4C65-B02F-F6C72164BC84@apache.org> X-Mailer: Apple Mail (2.3445.102.3) Holy =E2=80=A6 ! It does kill other test processes! In test-github-pr.sh: "### Kill any rogue build processes from the last attempt=E2=80=9D 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? Andor > On 2019. Jan 3., at 22:49, Enrico Olivelli = wrote: >=20 > 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 >=20 >=20 > Enrico >=20 > Il gio 3 gen 2019, 13:35 Andor Molnar ha scritto: >=20 >> Hi team, >>=20 >> I=E2=80=99m 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: >>=20 >> https://issues.apache.org/jira/browse/INFRA-17533 < >> https://issues.apache.org/jira/browse/INFRA-17533> >>=20 >> Regards, >> Andor >>=20 >>=20 >> -- >=20 >=20 > -- Enrico Olivelli