From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuri Weinstein Subject: Re: timeout 120 teuthology-killl is highly recommended Date: Tue, 21 Jul 2015 12:33:26 -0400 (EDT) Message-ID: <1312196360.1870726.1437496406379.JavaMail.zimbra@redhat.com> References: <55AE6F90.3070503@dachary.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mx4-phx2.redhat.com ([209.132.183.25]:51887 "EHLO mx4-phx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932313AbbGUQe2 convert rfc822-to-8bit (ORCPT ); Tue, 21 Jul 2015 12:34:28 -0400 In-Reply-To: <55AE6F90.3070503@dachary.org> Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Loic Dachary Cc: Ceph Development Loic I don't use teuthology-kill simultaneously only sequentially. As far as run time, just as a note, when we use 'stale' arg and it invo= kes ipmitool interface it does take awhile to finish.=20 Thx YuriW ----- Original Message ----- =46rom: "Loic Dachary" To: "Ceph Development" Sent: Tuesday, July 21, 2015 9:13:04 AM Subject: timeout 120 teuthology-killl is highly recommended Hi Ceph, Today I did something wrong and that blocked the lab for a good half ho= ur.=20 a) I ran two teuthology-kill simultaneously and that makes them deadloc= k each other b) I let them run unattended only to come back to the terminal 30 minut= es later and see them stuck. Sure, two teuthology-kill simultaneously should not deadlock and that n= eeds to be fixed. But the easy workaround to avoid that trouble is to j= ust not let it run forever. Even for ~200 jobs it takes at most a minut= e or two. And if it takes longer it probably means another teuthology-k= ill competes and it should be interrupted and restarted later. From now= on I'll do timeout 120 teuthology-kill .... || echo FAIL! as a generic safeguard. Apologies for the troubles. --=20 Lo=C3=AFc Dachary, Artisan Logiciel Libre -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html