From owner-freebsd-testing@freebsd.org Wed Feb 14 17:28:37 2018 Return-Path: Delivered-To: freebsd-testing@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F001F10994 for ; Wed, 14 Feb 2018 17:28:37 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E836483815 for ; Wed, 14 Feb 2018 17:28:36 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22b.google.com with SMTP id t79so30525857lfe.3 for ; Wed, 14 Feb 2018 09:28:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=+I3FZ5P8KYdEeHUMwtkqEHn4dX1x0xq4M0DZEqAGikQ=; b=WkVlXWk/EIjf4+x4x3/qc2rE50hJilnwsdmo0za0lv1GjguyCXv7Ir0inFvy/ira4c yftF2RmASSbNhFbUr9lrBqVq257ETt2NQfA9k4RBzxkqnve05FhDg0b0PnCa2LF+TO6c HOo+9jKQSHDl+hreJnaPKWjCmKbukxj4Ww7zgThfSGbjvlprK80E9tQPtMM/Ssr30Mrq rvPJwX4UpZxFV+/U1qXJuzzV1kH/nKNsy2I7iWQ43Cmt1LlpbWVurEuO4u443XZCL1Dr ZKYd2AyNguc+mmM2OcTnWZneLd1XNt8a/C2+B2wy3VPyQ94Nan6tjFPBWEJ64lmrurFm 95GA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=+I3FZ5P8KYdEeHUMwtkqEHn4dX1x0xq4M0DZEqAGikQ=; b=Jajs2iu7QxFZpBNhoeA7uij9bUDeXAr/Kqy3jSpDu/c628ykcPpfQcEdxXCyS0ccJ3 oI6CRWrYwxcNnyCnPhU/PoWSEfWADhg6ZycXLKTaI5t+BUJRFk3xERoUWPbjWwEaCj7P 3b0JwW3ndmEQEgvFlk26CRbw4gBgB+GMYwvLhE78Ub0W8drx+ODIGKftd3VMZNkAhXJt rJ80XZMyPdtK0HVEvTja65fHpEVuEG/b/Kc8b7UFagumjViGtkEDJf80DbVBgOKlXZd2 li2rSIggvy0PxUdakXqWTfmVcNBVZ3QJ/aBOGy/TF+y/ntrZxsRCsNhQNfpW1wNzsR57 k5Ig== X-Gm-Message-State: APf1xPCHDS0lDKSoMv847ZEN8TUNpAIJiAPkrK9TbtzQbzAv14byfnQV i8HBYpIfIq+4X0gCqQOKSmVFX4PyMcKHQR9ZbFY= X-Google-Smtp-Source: AH8x224nfxDfQomTtPgnJ3cI+CPqsHaMORsYnCiq5+hg7pRdbUVM3Mq988Pwb4MuvReSqemjSkuNJQHCtyQn6LriQhE= X-Received: by 10.25.166.209 with SMTP id p200mr4143470lfe.90.1518629314924; Wed, 14 Feb 2018 09:28:34 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.30.35 with HTTP; Wed, 14 Feb 2018 09:28:34 -0800 (PST) From: Alan Somers Date: Wed, 14 Feb 2018 10:28:34 -0700 X-Google-Sender-Auth: 72z4AT4Kk9X6Titp6ibk_IgfhwM Message-ID: Subject: Adjusting the timeout for the cleanup phase of an ATF test To: "freebsd-testing@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 17:28:37 -0000 How does one increase the timeout for the cleanup phase of an ATF test? The "cleanup" variable seems to affect only the test's body, not its cleanup. AFAICT the cleanup phase has a hardcoded 60s timeout. However, I have a test that legitimately takes about 65s to cleanup. ATF is killing it while the cleanup is still incomplete, and it leaves turds behind. Is there anyway to increase that limit? If not, I'll have to move part of the cleanup into the test body, which is ugly. -Alan