Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cCwQg-00037B-Vm for buildfarm-members@arkaria.postgresql.org; Fri, 02 Dec 2016 22:35:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cCwQg-0000iq-IG for buildfarm-members@arkaria.postgresql.org; Fri, 02 Dec 2016 22:35:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cCwQg-0000iA-CX for buildfarm-members@postgresql.org; Fri, 02 Dec 2016 22:35:42 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cCwQd-0002KF-UA for buildfarm-members@postgresql.org; Fri, 02 Dec 2016 22:35:41 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id uB2MZcf4000524 for ; Fri, 2 Dec 2016 17:35:38 -0500 From: Tom Lane To: buildfarm-members@postgresql.org Subject: Sigh, I pushed an infinite-loop test in HEAD MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <522.1480718138.1@sss.pgh.pa.us> Date: Fri, 02 Dec 2016 17:35:38 -0500 Message-ID: <523.1480718138@sss.pgh.pa.us> X-Pg-Spam-Score: -4.8 (----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: buildfarm-members Precedence: bulk Sender: buildfarm-members-owner@postgresql.org Slower PG buildfarm members might find that the test I added in commit b3427dade14cc31eb48740bc9ea98b5954470b24 proves to be an infinite loop. If your critter would have started a run in the last two hours or so, please check it and see if there's a postgres process that's consuming 100% CPU and has been for more than a minute or so. If so, "kill -TERM" should be enough to fix it. I've pushed a correction, so tests starting in future should be fine. Sorry about that :-( regards, tom lane -- Sent via buildfarm-members mailing list (buildfarm-members@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/buildfarm-members