From owner-freebsd-testing@FreeBSD.ORG Mon Sep 29 18:09:19 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D01AB29 for ; Mon, 29 Sep 2014 18:09:19 +0000 (UTC) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D6C8E75 for ; Mon, 29 Sep 2014 18:09:18 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id m8so13546726obr.6 for ; Mon, 29 Sep 2014 11:09:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=NMjCBM6+mGRv1Nq+izfC4aSekWAvul7oMZiz+mkgnVo=; b=iRS/9+V3Xzxz62iijV/wZGiRGmduPfY5jTZxTNjrn7nDlThYd6VNyrD+3dtQZE0AP3 KoPfB+3wBTBZc7MzzqCq9ifTLzX5h1Vuev347zmGIcBubLgYyZ8y9DRUa+SwI78DjYPv RiS8iAyscJgNKK7ESo4xAWBP7PgHwZ5eF1b018MB4ADIXRQoY3yLLZf+ScTQIJfZmMCA 6PaaCyGzuNGKywoLvoIMdtE4+hcK4peklc34nee7nsCrXfCNGox/bhs1yvzuw/H5vhQR lzkpkHjEp/luRhknkHvwPe9QgSQ4SqBhKnJ8Gu3CwgiPSDPF2A50+oo8/zpTfbAOz0sD A/ng== MIME-Version: 1.0 X-Received: by 10.60.92.133 with SMTP id cm5mr35254091oeb.55.1412014158150; Mon, 29 Sep 2014 11:09:18 -0700 (PDT) Received: by 10.76.167.65 with HTTP; Mon, 29 Sep 2014 11:09:18 -0700 (PDT) Date: Mon, 29 Sep 2014 11:09:18 -0700 Message-ID: Subject: Increasing timeout for ATF test case From: Shrikanth Kamath To: freebsd-testing@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 18:09:19 -0000 I am running a python script from inside ATF test framework but because of some default timeout it does not allow the python script to run to completion. Getting the following error... tc-end: 1411774809.781712, dtest, failed, Test case timed out after 300 seconds How do I increase the timeout in ATF test case? -- Shrikanth R K From owner-freebsd-testing@FreeBSD.ORG Mon Sep 29 19:38:31 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F6D8C61 for ; Mon, 29 Sep 2014 19:38:31 +0000 (UTC) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AA5FBA3 for ; Mon, 29 Sep 2014 19:38:30 +0000 (UTC) Received: by mail-la0-f44.google.com with SMTP id gi9so8532715lab.3 for ; Mon, 29 Sep 2014 12:38:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=/PSHdGlgTZ6J8OmZoLRE8af46cYAgE7XyNBRKlJkMt4=; b=FTy8WUNE1aWMZMkMGANEa56i6zjOCwyY1HNukEfYmv1QDnetLXE3LTPJq0ypOn6tof 3zQoIe8jXt/mU1zWZAYv//j7jA0hulpcl4S5tFfAW1d72ISXwvTAR/5W4c/cGFGf0gY8 3UnsD3Yf3bCa+vsh434MDe0aV5b1OnwxnQcMFguTiRaD0WwE9+TW6uG1PmnoOpoyCrNW 73bc0qUKrMsx91bRmqnKSesffXJbqUcbp8y9wBYLRWHSH4Pac8zx+zD1CMebFCBVNqMQ 8x6V2xn0lq8ATx9ZBR7zxvZKHFMaQqVmAFnQsx6+H9+AYz0oKpybonv2kWG8eAYqL/9q G2aA== MIME-Version: 1.0 X-Received: by 10.152.20.1 with SMTP id j1mr41445311lae.57.1412019508206; Mon, 29 Sep 2014 12:38:28 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.131.66 with HTTP; Mon, 29 Sep 2014 12:38:28 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Sep 2014 12:38:28 -0700 X-Google-Sender-Auth: CnPOyxkVvbY-4ZiZ_X_dcXosd4Q Message-ID: Subject: Re: Increasing timeout for ATF test case From: Craig Rodrigues To: Shrikanth Kamath Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 19:38:31 -0000 Hi, How are you running the tests? If you use kyua, you can specify the timeout for an individual test in the Kyuafile: http://manned.org/kyuafile.5 -- Craig On Mon, Sep 29, 2014 at 11:09 AM, Shrikanth Kamath wrote: > I am running a python script from inside ATF test framework but > because of some default timeout it does not allow the python script to > run to completion. > Getting the following error... > tc-end: 1411774809.781712, dtest, failed, Test case timed out after 300 > seconds > > How do I increase the timeout in ATF test case? > > -- > Shrikanth R K > _______________________________________________ > freebsd-testing@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-testing > To unsubscribe, send any mail to "freebsd-testing-unsubscribe@freebsd.org" > From owner-freebsd-testing@FreeBSD.ORG Mon Sep 29 20:17:12 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E07DBB80; Mon, 29 Sep 2014 20:17:12 +0000 (UTC) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A247195; Mon, 29 Sep 2014 20:17:12 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id vb8so2827241obc.36 for ; Mon, 29 Sep 2014 13:17:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lqufPJyH4uf3CsLjUipMrbXaIMnb9V8aNMsa0OWq+gs=; b=g3jCXLGNmFkvvKY5H3Q7/+T0bUspvEbZdA9zkQinNe+JwciDSo1Z+wff2SzGtRVpjw BRJZwV8uQ7XauAgqCPSteWQYoixk+oxdR5f36bIWThm2p03aS4+xzFLEr9KmhsSItyUp /89NFcgABY08o3OTqmVHT0GgAasyGwLnQEcG7nMy2m8usUV1UIe47TTy8wFXEBhoYCx4 TVSzw95O0pulqAFjjgj/oxU6JY/06uBE02ml3d0mWqahpipn2JPtB3liu53lRJr6ylcl yn2Wy9NABM3aCHInzOhGqXt4LEeLDH45sZNzWdUHNgVJwlOHHZonX3gML7bOkqIrjCCI VIuw== MIME-Version: 1.0 X-Received: by 10.60.51.227 with SMTP id n3mr41969559oeo.52.1412021831901; Mon, 29 Sep 2014 13:17:11 -0700 (PDT) Received: by 10.76.167.65 with HTTP; Mon, 29 Sep 2014 13:17:11 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Sep 2014 13:17:11 -0700 Message-ID: Subject: Re: Increasing timeout for ATF test case From: Shrikanth Kamath To: Craig Rodrigues Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 20:17:13 -0000 Hi Craig, Not using kyua yet...I run the test by just issuing %atf-run t_dtest -- Shrikanth R K On Mon, Sep 29, 2014 at 12:38 PM, Craig Rodrigues wrote: > Hi, > > How are you running the tests? > If you use kyua, you can specify the timeout for an individual test in the > Kyuafile: http://manned.org/kyuafile.5 > > -- > Craig > > > On Mon, Sep 29, 2014 at 11:09 AM, Shrikanth Kamath > wrote: >> >> I am running a python script from inside ATF test framework but >> because of some default timeout it does not allow the python script to >> run to completion. >> Getting the following error... >> tc-end: 1411774809.781712, dtest, failed, Test case timed out after 300 >> seconds >> >> How do I increase the timeout in ATF test case? >> >> -- >> Shrikanth R K >> _______________________________________________ >> freebsd-testing@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-testing >> To unsubscribe, send any mail to "freebsd-testing-unsubscribe@freebsd.org" > > From owner-freebsd-testing@FreeBSD.ORG Mon Sep 29 20:58:31 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A757AA79 for ; Mon, 29 Sep 2014 20:58:31 +0000 (UTC) Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3074B6C3 for ; Mon, 29 Sep 2014 20:58:31 +0000 (UTC) Received: by mail-la0-f48.google.com with SMTP id q1so7314535lam.35 for ; Mon, 29 Sep 2014 13:58:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=MEEYoGdhgNcWbKe7NMdOZ0YDcIDD/qQYOH2giG1lgxI=; b=tmRlbpVTUvjmPtpxS23jRH/MldPdY7uYm2dI0uxAv7UJdF6MUe26JIbZHos/HYJoWh uAxEwMpaKzF1TkU5zxHn8xyYeYcKJt+7lfHnnqcADJiUsxOKu328fzRVfCThatq1TJSl jzoexOT3AEYjmheiaSncZergnzimPvKUWwlAzZhB+4veHiILC1SklSC5RQtRSY/pW3XY HjsrmHtcilXGLI0LsdweT1XNGzFV04++joXfj5rY/68l4Kt/7KQgkIarLsDpRMGD9pfd n50lFeDfpzVo2yqqJdmS5F5cPCjHMwTUpcgapVMxtooiJnVSxvv2sqNKWfnVd+Aa5ZJd k8JA== MIME-Version: 1.0 X-Received: by 10.112.199.232 with SMTP id jn8mr39519441lbc.30.1412024309031; Mon, 29 Sep 2014 13:58:29 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.131.66 with HTTP; Mon, 29 Sep 2014 13:58:29 -0700 (PDT) Date: Mon, 29 Sep 2014 13:58:29 -0700 X-Google-Sender-Auth: uywtrTyYCkEg00WsoirjvrDtpkI Message-ID: Subject: Re: Increasing timeout for ATF test case From: Craig Rodrigues To: Shrikanth Kamath Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 20:58:31 -0000 Hi, I'm not sure, but you might be able to put something like this in the _head() method for your testcase: atf_set "timeout" "500" See: http://www.daemon-systems.org/man/atf-test-case.4.html Keep in mind that in atf 0.20, the atf-run program has been removed, and kyua is the preferred way to run ATF tests. You might want to glance at this document that I am writing and provide feedback: https://github.com/rodrigc/kyua/wiki/Quickstart-Guide -- Craig On Mon, Sep 29, 2014 at 1:16 PM, Shrikanth Kamath wrote: > Hi Craig, > Not using kyua yet...I run the test by just issuing > > %atf-run t_dtest > > -- > Shrikanth R K > > On Mon, Sep 29, 2014 at 12:38 PM, Craig Rodrigues > wrote: > > Hi, > > > > How are you running the tests? > > If you use kyua, you can specify the timeout for an individual test in > the > > Kyuafile: http://manned.org/kyuafile.5 > > > > -- > > Craig > > > > > > On Mon, Sep 29, 2014 at 11:09 AM, Shrikanth Kamath < > shrikanth07@gmail.com> > > wrote: > >> > >> I am running a python script from inside ATF test framework but > >> because of some default timeout it does not allow the python script to > >> run to completion. > >> Getting the following error... > >> tc-end: 1411774809.781712, dtest, failed, Test case timed out after 300 > >> seconds > >> > >> How do I increase the timeout in ATF test case? > >> > >> -- > >> Shrikanth R K > >> _______________________________________________ > >> freebsd-testing@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-testing > >> To unsubscribe, send any mail to " > freebsd-testing-unsubscribe@freebsd.org" > > > > > From owner-freebsd-testing@FreeBSD.ORG Mon Sep 29 21:55:32 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 688DD46B; Mon, 29 Sep 2014 21:55:32 +0000 (UTC) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 29898D3F; Mon, 29 Sep 2014 21:55:32 +0000 (UTC) Received: by mail-oi0-f46.google.com with SMTP id h136so2800021oig.33 for ; Mon, 29 Sep 2014 14:55:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6RFCK1rhN9O3U0XhqwL2cgj7p+rxMcIjZyb3Z7duzlw=; b=H8pSF4O+CdrPHvW8OgBWS3KpZGxc4Lj7mUQ8+jH6u2rikhHFuN1+1eYQBHNfySecAG d1jyMCvydx8rCVg9Z/nMra/CSDUAmPdzH7ZY3Wm9wy8IFN2QCph6//EIE8/StaDw8QwP qo6sip22w4n4Y6jKoRDo4tg7H5eQwfq2HJ3NtYbw+N+7qfdhb+P3vlCwlH/bnE4dQGfj +R9NVqggcvek3HcSbJtD3Srvqg0EmWF0bf+CyKPvBlhi3EgMBMjI/pLXCPLysflA7rnD 3zfHVHzFx/kPv2BdxJsZlei4dHViJRZVTXNcsYWg+m36sge9XeSAPy58/8sjJW2zxe7B MoqA== MIME-Version: 1.0 X-Received: by 10.182.22.233 with SMTP id h9mr43018155obf.48.1412027731486; Mon, 29 Sep 2014 14:55:31 -0700 (PDT) Received: by 10.76.167.65 with HTTP; Mon, 29 Sep 2014 14:55:31 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Sep 2014 14:55:31 -0700 Message-ID: Subject: Re: Increasing timeout for ATF test case From: Shrikanth Kamath To: Craig Rodrigues Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 21:55:32 -0000 Thanks Craig, that solved it. I have to start reading on kyua but currently the availability in my env is still the legacy atf-run I had a follow up question, does ATF framework support signaling the test scripts like a SIGINT? Or I have to take help from a wrapper shell script? -- Shrikanth R K On Mon, Sep 29, 2014 at 1:58 PM, Craig Rodrigues wrote: > Hi, > > I'm not sure, but you might be able to put > something like this in the _head() method for your testcase: > > atf_set "timeout" "500" > > See: http://www.daemon-systems.org/man/atf-test-case.4.html > > > Keep in mind that in atf 0.20, the atf-run program has been > removed, and kyua is the preferred way to run ATF tests. > > You might want to glance at this document that I am writing and provide > feedback: > > https://github.com/rodrigc/kyua/wiki/Quickstart-Guide > > -- > Craig > > > > > > > On Mon, Sep 29, 2014 at 1:16 PM, Shrikanth Kamath > wrote: >> >> Hi Craig, >> Not using kyua yet...I run the test by just issuing >> >> %atf-run t_dtest >> >> -- >> Shrikanth R K >> >> On Mon, Sep 29, 2014 at 12:38 PM, Craig Rodrigues >> wrote: >> > Hi, >> > >> > How are you running the tests? >> > If you use kyua, you can specify the timeout for an individual test in >> > the >> > Kyuafile: http://manned.org/kyuafile.5 >> > >> > -- >> > Craig >> > >> > >> > On Mon, Sep 29, 2014 at 11:09 AM, Shrikanth Kamath >> > >> > wrote: >> >> >> >> I am running a python script from inside ATF test framework but >> >> because of some default timeout it does not allow the python script to >> >> run to completion. >> >> Getting the following error... >> >> tc-end: 1411774809.781712, dtest, failed, Test case timed out after 300 >> >> seconds >> >> >> >> How do I increase the timeout in ATF test case? >> >> >> >> -- >> >> Shrikanth R K >> >> _______________________________________________ >> >> freebsd-testing@freebsd.org mailing list >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-testing >> >> To unsubscribe, send any mail to >> >> "freebsd-testing-unsubscribe@freebsd.org" >> > >> > > > From owner-freebsd-testing@FreeBSD.ORG Tue Sep 30 08:54:07 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AFB44836 for ; Tue, 30 Sep 2014 08:54:07 +0000 (UTC) Received: from mail-we0-f175.google.com (mail-we0-f175.google.com [74.125.82.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 483A3607 for ; Tue, 30 Sep 2014 08:54:06 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id q59so3332122wes.6 for ; Tue, 30 Sep 2014 01:53:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=nr6txILib5tpboC86k+QLonoQPHkCbA3VEzL+4AlGNA=; b=O+53hHpQRbG06/kxPcnLelWX+3cBV3g324WX7m0KfX+hR9Ey7Gp3N8jmafkDOWxQsf wxTA53i+MD3JoDD8qqGVf3PJhUCyirN5D6yU/dBdiTipSxaTOzPwOGLAH9AtXcjkMKhq kosi/E21a0sLrLTIZtvl7utgCkY1odW+DdwCVleBRSUGz0mdCxr6m2fVftUJg8xh3xvi t6NxNKub1P9tMRuV6aBTwoyIMkoN/6+vl7xmOdzXAr4HFb7HfwNr1pwBnvom2TS/ONNn karUB32HiMcvW9NzHQJ/kmMQnuc8OsYRMJzLsdN/E4yeHY7VSBhpE86UBvNSE4IRdG+r Jjfg== X-Gm-Message-State: ALoCoQnh3acL+gJSZrSd4k4to+UYdJmi+TdskBHYnw3m8ny88DordaDCeEWDrJ5ycDJ2eVwNyCX7 X-Received: by 10.180.79.34 with SMTP id g2mr4103163wix.10.1412067239526; Tue, 30 Sep 2014 01:53:59 -0700 (PDT) MIME-Version: 1.0 Sender: jmmv@meroh.net Received: by 10.194.74.201 with HTTP; Tue, 30 Sep 2014 01:53:39 -0700 (PDT) X-Originating-IP: [77.241.230.246] In-Reply-To: References: From: Julio Merino Date: Tue, 30 Sep 2014 11:53:39 +0300 X-Google-Sender-Auth: UKZdp3wKuSJKSoHu7Fa48vnCe38 Message-ID: Subject: Re: Increasing timeout for ATF test case To: Shrikanth Kamath Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 08:54:07 -0000 On Tue, Sep 30, 2014 at 12:55 AM, Shrikanth Kamath wrote: > Thanks Craig, that solved it. I have to start reading on kyua but > currently the availability in my env is still the legacy atf-run I had > a follow up question, does ATF framework support signaling the test > scripts like a SIGINT? Or I have to take help from a wrapper shell > script? What do you mean? Signaling the script with SIGINT when? From owner-freebsd-testing@FreeBSD.ORG Thu Oct 2 08:22:58 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8C4983C2; Thu, 2 Oct 2014 08:22:58 +0000 (UTC) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B8234BB2; Thu, 2 Oct 2014 08:22:57 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id mk6so1926581lab.1 for ; Thu, 02 Oct 2014 01:22:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=oEWjuxV1YXWU0Er6fXqHlyPLnAYR2IYVAuUnSL/z0GU=; b=ZHW+gpFFj8dr5HH55B1BaAkTCw5W/6NGZhMSh/LITwqwiIGEzatseZYg8cByA2pAsr kuPnkENpBvG7dw4IOS/pwn/hlip3pYGrwljzxGCx1SUxGxjsgySLiCKlJp6rbOShspyk iP6rtHFBm+AxFc1Koc47+XIB4RtOpBp3dsemB+f4JHvbCbS1eC4sRh0ymVuVvyDyL/x2 pVgm6TqYEdmvDyu9PIBz6dy1ria2+IkaIjwIhObPlKdsElZOVBBRO0BiG/1N3pyNafMY 4YuIjExAWdlDEN3+HnZN8wl93iUqB/XgGc7te5V7Que52hbJq4loZ86QrdWLmIg7V7bD UTfw== MIME-Version: 1.0 X-Received: by 10.112.134.101 with SMTP id pj5mr57378408lbb.47.1412238175798; Thu, 02 Oct 2014 01:22:55 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.131.66 with HTTP; Thu, 2 Oct 2014 01:22:55 -0700 (PDT) Date: Thu, 2 Oct 2014 01:22:55 -0700 X-Google-Sender-Auth: PfEbI8VV8wvxFTA96QBzciEt8X4 Message-ID: Subject: Integrating pkg test results into Jenkins From: Craig Rodrigues To: Steve Wills Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , freebsd-pkg@freebsd.org X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 08:22:58 -0000 Hi, I notice that at http://jenkins.mouf.net/job/pkg/ you are using kyua to test pkg. Instead of producing an HTML page of the test results, you may wish to integrate the output of the tests directly into Jenkins. You can do this by: (1) In your Jenkins job's Build section, add this to the end: set +e # You don't want the job to abort here if kyua returns # non-zero status due to any test failurs kyua test kyua_status=$? set -e kyua report-junit --output=$WORKSPACE/test-report.xml exit $kyua_status (2) In your Jenkins job's Post-Build Actions, add: "Publish JUnit test result report" "Test Report XMLs" -> test-report.xml The end result is quite nice, and looks like this: https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport/ -- Craig From owner-freebsd-testing@FreeBSD.ORG Thu Oct 2 09:23:04 2014 Return-Path: Delivered-To: testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 912A83B5; Thu, 2 Oct 2014 09:23:04 +0000 (UTC) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E6BE825D; Thu, 2 Oct 2014 09:23:03 +0000 (UTC) Received: by mail-la0-f47.google.com with SMTP id pv20so2013336lab.34 for ; Thu, 02 Oct 2014 02:23:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=XSwE0OMPOqKU7ToKve5yQazyw7WQj+C5H0q6kF8UH0E=; b=PdAJDfxdxohjpTYODBNggrwlCzQ3oewICfybIGFewkJ2YRSUyKU+LdYldTcdtUqh9w gWAk1kdev89hTQD5OtF3uzSnDx/hG5/IUXyzZ/ePQV3O8LYpqY6ZSqagc0plnUqJaY97 lTnrox+N5EYFB0sd5VqLos+KoQuGDn30lxxaYafkxh90rjhH1sPL3prsEMzrGxFrjSU3 Fd6k6YxTBAQZmmRJ8mZ2Fto4JcTMeSZnYj+iJp7XtOy7prKYKTYdlKYWDURc08gMaY13 fW7XP8j46wwn58+VQWYDLe7xn08KD1rhpUGDF7oJtm/cOOKT6DLEI9bFQ22/aXVcvs2W 7Qhg== MIME-Version: 1.0 X-Received: by 10.112.54.130 with SMTP id j2mr28041612lbp.41.1412241781787; Thu, 02 Oct 2014 02:23:01 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.131.66 with HTTP; Thu, 2 Oct 2014 02:23:01 -0700 (PDT) Date: Thu, 2 Oct 2014 02:23:01 -0700 X-Google-Sender-Auth: B8gCUADVG-8vKYfNMq8K_SGUQic Message-ID: Subject: Need help debugging yacc test failure in CURRENT From: Craig Rodrigues To: freebsd-current Current , "freebsd-testing@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 09:23:04 -0000 Hi, I have managed to eliminate all the test failures from /usr/tests in CURRENT except for one failure. See: https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport/ I can reproduce the failure by doing the following: mkdir /tmp/x cd /tmp/x /usr/tests/usr.bin/yacc/yacc_tests usr.bin.yacc.yacc_tests.main I then get a core file: /tmp/x/test/yacc.core Can someone help debug and fix this? Thanks. -- Craig From owner-freebsd-testing@FreeBSD.ORG Thu Oct 2 09:52:50 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C3F3AFA; Thu, 2 Oct 2014 09:52:50 +0000 (UTC) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 459A27B3; Thu, 2 Oct 2014 09:52:49 +0000 (UTC) Received: by mail-la0-f47.google.com with SMTP id pv20so1965386lab.20 for ; Thu, 02 Oct 2014 02:52:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=MOka2W20ldZ5NI7SHMEnMAZGWV9jQcecWLxBHsScc7s=; b=BODRveUWhtjL1kuaFkh8TBB89fy/AC+llLIc949ELMQosM3JEBE0IYSzaOxVP3oovP DQxYgxAuqlgBHOti5JeDjCG1Kp2plmtYr53puarVbkV9tGobdvyfkMJxYVJs4Uva9lFT p3dWmrDWdbBYdh9OmrJl637SdOlEF5O4lCzTUoYpmSzXjJcXRLH+6BSaVgWAkSoXabHL DMWCqh6LCYjmNwVXc8cb8r2evTkokP+FlkzpUmrwnVZIQIu4wBday8AJWs3/jDHF51Xj Al8Wc81H044UX6r2hllD3CAqeD7uI9mL9IbAxre0/d9oNVBMfQpnUmT/4Z43QJQtYFGp u8lQ== MIME-Version: 1.0 X-Received: by 10.152.28.38 with SMTP id y6mr25969948lag.90.1412243567319; Thu, 02 Oct 2014 02:52:47 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.131.66 with HTTP; Thu, 2 Oct 2014 02:52:47 -0700 (PDT) Date: Thu, 2 Oct 2014 02:52:47 -0700 X-Google-Sender-Auth: E7gNcnfdrnNncnYkst4EPK-8SFs Message-ID: Subject: One patch pushed upstream to Jenkins From: Craig Rodrigues To: "jenkins-admin@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , "freebsd-java@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 09:52:50 -0000 Hi, One of my patches to upgrade the Java Native Access (JNA) 4.1.0 library in Jenkins got accepted: https://github.com/jenkinsci/jenkins/pull/1410 This patch is still pending: https://github.com/jenkinsci/jenkins/pull/1387 JNA 4.1.0 fixes some bugs on FreeBSD, so I am hoping that it will get accepted. -- Craig From owner-freebsd-testing@FreeBSD.ORG Thu Oct 2 17:57:04 2014 Return-Path: Delivered-To: testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E088F688 for ; Thu, 2 Oct 2014 17:57:04 +0000 (UTC) Received: from mail-qg0-f45.google.com (mail-qg0-f45.google.com [209.85.192.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A00A4931 for ; Thu, 2 Oct 2014 17:57:04 +0000 (UTC) Received: by mail-qg0-f45.google.com with SMTP id e89so2313572qgf.18 for ; Thu, 02 Oct 2014 10:57:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=Stce99MZurYjhmAtIGBjT2nZ9de9LkobVz3TyM4/KXE=; b=QVyJqy4+IPRP8CeHufSR6Ieo2Exrihks7ZesN8nTuFtnhl8Hz+7hXz92354e3UK9LM 7ktB2f43eTskKZQyWN+wtzCSMGReX9BEGaFX1F0o9zzlRDCYCGcX/t/LjJiybU9AvyAZ piwggiS2AMXj7Es51Y3CM4Z78O8LGfc9OMGwaynPGsoga2BluUtF58L59fsN1PL9aBjE ovtvDnFO+qyuD+BKWyrnJh6eckCAp1xpIfaes6MfJqiSGsed6Xclz7mmgB/vTtQVWPoV HIhdIjp7hSzIhZvLxoZAl5posEBZgGSKGoe/VPrjaZAcHfU254bidIy8czV3Bqsw1kLP K3YQ== X-Gm-Message-State: ALoCoQmvTMmO/Anwpd2j8HOY/cercRQnpNrVAFhJq1lzSXNcJ0QD2jU4+nxVaepJoD4eBX/CnXHs X-Received: by 10.140.92.199 with SMTP id b65mr667160qge.86.1412272622640; Thu, 02 Oct 2014 10:57:02 -0700 (PDT) MIME-Version: 1.0 Sender: jmmv@meroh.net Received: by 10.96.75.134 with HTTP; Thu, 2 Oct 2014 10:56:42 -0700 (PDT) X-Originating-IP: [2620:0:1003:1007:f94e:df22:a7b5:d386] In-Reply-To: References: From: Julio Merino Date: Thu, 2 Oct 2014 13:56:42 -0400 X-Google-Sender-Auth: lO0e1XfCzo1Y0LXfhgExJlghWY0 Message-ID: Subject: Re: Need help debugging yacc test failure in CURRENT To: Craig Rodrigues Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current Current , "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 17:57:05 -0000 On Thu, Oct 2, 2014 at 5:23 AM, Craig Rodrigues wrote: > Hi, > > I have managed to eliminate all the test failures from /usr/tests in CURRENT > except for one failure. See: > > https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport/ > > I can reproduce the failure by doing the following: > > mkdir /tmp/x > cd /tmp/x > /usr/tests/usr.bin/yacc/yacc_tests usr.bin.yacc.yacc_tests.main > > I then get a core file: /tmp/x/test/yacc.core > > Can someone help debug and fix this? What you'd do until someone fixes the yacc bug is file a PR for this crash and then mark the test as "expected failure" (or TODO in TAP terms). From owner-freebsd-testing@FreeBSD.ORG Thu Oct 2 18:10:21 2014 Return-Path: Delivered-To: testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17CBDBC; Thu, 2 Oct 2014 18:10:21 +0000 (UTC) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C369AA9B; Thu, 2 Oct 2014 18:10:20 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id lf10so3054060pab.16 for ; Thu, 02 Oct 2014 11:10:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=soDkSsiG5V1BUk0l9OZmhoztRQNYizQLdnL33x78Lr8=; b=K9tQ8oEsAZk6Q+XXUE7MmuxsKTM52BO2cy+xS2od/T0BcXk/OxGWTMBH3dUUQf6fcy OOZ0mRsru8LevXkUUhG9+sst9mf9Ejhb6y1n9wcbNMC//chdaQf5V8cvu9Wn+7hFba7R J0yQ0SmzF5nKGX6b2iqtZFQOOI/4IyxoWZvGd1b5PwI4+xJlc+4qCNd+15C1lzad3a5D yGj9S/9PKgDBT7gkDLZL9A2TMu58ONms6xlFjC8NQgaayeUI2E7v1/vngBZrlR925hgH hL9j5GLtZ0kuzvbEBgKbBqYzO4msXIUmVKWDfbomb5U6t3jSa25OZouUhxDSy+hqPdO9 YiBA== X-Received: by 10.68.68.131 with SMTP id w3mr515541pbt.93.1412273420249; Thu, 02 Oct 2014 11:10:20 -0700 (PDT) Received: from [192.168.20.11] (c-98-247-240-204.hsd1.wa.comcast.net. [98.247.240.204]) by mx.google.com with ESMTPSA id b2sm2427862pbu.42.2014.10.02.11.10.19 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 11:10:19 -0700 (PDT) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <8E14869A-049B-4BBA-BE51-714AD202F191@gmail.com> X-Mailer: iPhone Mail (11D257) From: Garrett Cooper Subject: Re: Need help debugging yacc test failure in CURRENT Date: Thu, 2 Oct 2014 11:10:19 -0700 To: Julio Merino Cc: Baptiste Daroussin , freebsd-current Current , "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 18:10:21 -0000 > On Oct 2, 2014, at 10:56, Julio Merino wrote: >=20 >> On Thu, Oct 2, 2014 at 5:23 AM, Craig Rodrigues wro= te: >> Hi, >>=20 >> I have managed to eliminate all the test failures from /usr/tests in CURR= ENT >> except for one failure. See: >>=20 >> https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport/= >>=20 >> I can reproduce the failure by doing the following: >>=20 >> mkdir /tmp/x >> cd /tmp/x >> /usr/tests/usr.bin/yacc/yacc_tests usr.bin.yacc.yacc_tests.main >>=20 >> I then get a core file: /tmp/x/test/yacc.core >>=20 >> Can someone help debug and fix this? >=20 > What you'd do until someone fixes the yacc bug is file a PR for this > crash and then mark the test as "expected failure" (or TODO in TAP > terms). There already is a bug (look or bugs I filed related to yacc). Someone broke= behavior in the kernel or libc that yacc depends on.= From owner-freebsd-testing@FreeBSD.ORG Thu Oct 2 18:14:20 2014 Return-Path: Delivered-To: testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3336A570; Thu, 2 Oct 2014 18:14:20 +0000 (UTC) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E37D3B74; Thu, 2 Oct 2014 18:14:19 +0000 (UTC) Received: by mail-pa0-f41.google.com with SMTP id eu11so3085771pac.28 for ; Thu, 02 Oct 2014 11:14:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=QWQ8L25jEUSh/OJsFH/urv+76F/w2C0VfIjoHg4shr0=; b=xwZbSQfzMqNMNv3Xo3ekMcyBpqZLjOpL9uvSJ4V6en+0bBh5wxeW0+Spls5IJ6KYTA 1IyB4kSoTYMWbO1Y+sK7XUaoGtTvJt8dWl9HnKseasjdUTDeLjle5glfSTO259PFJ6dn JTN74HVc8uaexae/XKjsOxi+3n7LcFoE66/eXW6xJK9fYT4ix4WXaHXC88nr7/gGqitE eX2ORB3AoUmSXUOUH+PpLsqcnrLoH6dXmWo3d2Qspt6a4oIHmf3v+yfV60gvO2287xXV OQZqTrA2lZ5xpQIX74dsdoFddANM7OfpQrzsj1aGyyVlqKX3sJQPfCG+3drRIAaVBFDb WSDA== X-Received: by 10.69.31.1 with SMTP id ki1mr782485pbd.100.1412273657998; Thu, 02 Oct 2014 11:14:17 -0700 (PDT) Received: from [192.168.20.11] (c-98-247-240-204.hsd1.wa.comcast.net. [98.247.240.204]) by mx.google.com with ESMTPSA id ot8sm4438660pbc.1.2014.10.02.11.14.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 11:14:17 -0700 (PDT) References: <8E14869A-049B-4BBA-BE51-714AD202F191@gmail.com> Mime-Version: 1.0 (1.0) In-Reply-To: <8E14869A-049B-4BBA-BE51-714AD202F191@gmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <3B9D64BE-9982-4334-B20B-E316A8361466@gmail.com> X-Mailer: iPhone Mail (11D257) From: Garrett Cooper Subject: Re: Need help debugging yacc test failure in CURRENT Date: Thu, 2 Oct 2014 11:14:17 -0700 To: Julio Merino Cc: Baptiste Daroussin , freebsd-current Current , "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 18:14:20 -0000 > On Oct 2, 2014, at 11:10, Garrett Cooper wrote: >=20 >=20 >>> On Oct 2, 2014, at 10:56, Julio Merino wrote: >>>=20 >>> On Thu, Oct 2, 2014 at 5:23 AM, Craig Rodrigues wr= ote: >>> Hi, >>>=20 >>> I have managed to eliminate all the test failures from /usr/tests in CUR= RENT >>> except for one failure. See: >>>=20 >>> https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport= / >>>=20 >>> I can reproduce the failure by doing the following: >>>=20 >>> mkdir /tmp/x >>> cd /tmp/x >>> /usr/tests/usr.bin/yacc/yacc_tests usr.bin.yacc.yacc_tests.main >>>=20 >>> I then get a core file: /tmp/x/test/yacc.core >>>=20 >>> Can someone help debug and fix this? >>=20 >> What you'd do until someone fixes the yacc bug is file a PR for this >> crash and then mark the test as "expected failure" (or TODO in TAP >> terms). >=20 > There already is a bug (look or bugs I filed related to yacc). Someone bro= ke behavior in the kernel or libc that yacc depends on. Let me rephrase that. Using an older atf/kyua didn't repro the bug, so it's p= robably atf/kyua= From owner-freebsd-testing@FreeBSD.ORG Thu Oct 2 20:55:11 2014 Return-Path: Delivered-To: testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4085EA7; Thu, 2 Oct 2014 20:55:11 +0000 (UTC) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DE189F8A; Thu, 2 Oct 2014 20:55:10 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id rl12so3324874iec.31 for ; Thu, 02 Oct 2014 13:55:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yCqemzT6P/tl0kYHABZTeAmYWyowto6vtkD3/nMSqP8=; b=v3BBxTKMpljvIL0v1PtojfsIZJFj6BNMVTuekXtrlXJjAHu8dHxhktXHS0U1rYt8k9 I7Umo+2FsSdYi0h0FoQqKYwA8l1xbDx6ejtvPr4+MoSSTUEvrenGojupMVX92klATyLF wCAA8GkQseP+rjKRGoEgBItjsa8BF2B8ap3VsGkI/kqLtQ7ejvg+tt11sSytPC0DMza4 EjDhhh+E0P9LnXk//l0zW2E2CP4t64QFns5HaNNesFvXh/NRDHhGuFEbg84REm8HUyyJ Y8yvROedfKqcarrwlOHo/VZVUba2iOQesSvYPcit7eITLgjb8PPqKVI1HqKa/WTSlWK+ iBTQ== MIME-Version: 1.0 X-Received: by 10.42.207.131 with SMTP id fy3mr8160117icb.67.1412283310316; Thu, 02 Oct 2014 13:55:10 -0700 (PDT) Received: by 10.50.227.42 with HTTP; Thu, 2 Oct 2014 13:55:10 -0700 (PDT) In-Reply-To: <3B9D64BE-9982-4334-B20B-E316A8361466@gmail.com> References: <8E14869A-049B-4BBA-BE51-714AD202F191@gmail.com> <3B9D64BE-9982-4334-B20B-E316A8361466@gmail.com> Date: Thu, 2 Oct 2014 13:55:10 -0700 Message-ID: Subject: Re: Need help debugging yacc test failure in CURRENT From: NGie Cooper To: Julio Merino Content-Type: text/plain; charset=UTF-8 Cc: Baptiste Daroussin , freebsd-current Current , "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 20:55:11 -0000 On Thu, Oct 2, 2014 at 11:14 AM, Garrett Cooper wrote: ... > Let me rephrase that. Using an older atf/kyua didn't repro the bug, so it's probably atf/kyua Here's the bug I was referring to: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499 (was replying on my phone earlier). Thanks! From owner-freebsd-testing@FreeBSD.ORG Thu Oct 2 21:05:38 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5736E636 for ; Thu, 2 Oct 2014 21:05:38 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3EF02139 for ; Thu, 2 Oct 2014 21:05:38 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s92L5cBM083578 for ; Thu, 2 Oct 2014 21:05:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-testing@freebsd.org Subject: [Bug 193499] [tests] usr.bin/yacc/err_syntax27.error failures with the latest kyua Date: Thu, 02 Oct 2014 21:05:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rodrigc@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-testing@freebsd.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 21:05:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499 Craig Rodrigues changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-testing@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-testing@FreeBSD.ORG Fri Oct 3 17:19:39 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4B5D44BC for ; Fri, 3 Oct 2014 17:19:39 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 325A1AD1 for ; Fri, 3 Oct 2014 17:19:39 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s93HJduH066781 for ; Fri, 3 Oct 2014 17:19:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-testing@freebsd.org Subject: [Bug 193499] [tests] usr.bin/yacc/err_syntax27.error failures with the latest kyua Date: Fri, 03 Oct 2014 17:19:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jmmv@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-testing@freebsd.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 17:19:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499 --- Comment #3 from Julio Merino,+1 347 694 0576,New York City --- I can't imagine how this can be a Kyua bug given that 1) the test is using the plain interface, 2) the output of the test points at differences in yacc output and 3) yacc crashed. But it seems that Garrett (?) has found a bug in yacc with valgrind so that may explain it. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-testing@FreeBSD.ORG Fri Oct 3 19:38:16 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 98D66F58 for ; Fri, 3 Oct 2014 19:38:16 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 80525C12 for ; Fri, 3 Oct 2014 19:38:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s93JcG5p070606 for ; Fri, 3 Oct 2014 19:38:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-testing@freebsd.org Subject: [Bug 193499] [tests] usr.bin/yacc/err_syntax27.error failures with the latest kyua Date: Fri, 03 Oct 2014 19:38:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rodrigc@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-testing@freebsd.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 19:38:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499 --- Comment #4 from Craig Rodrigues --- When I run this test, I get a coredump in yacc, so it is not a bug in kyua. When I look at the coredump, I get no symbols. I need to recompile yacc with debug symbols and provide the core. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-testing@FreeBSD.ORG Sat Oct 4 02:53:30 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2C4C6CC5; Sat, 4 Oct 2014 02:53:30 +0000 (UTC) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E0D5AFBB; Sat, 4 Oct 2014 02:53:29 +0000 (UTC) Received: from mouf.net (swills@mouf [199.48.129.64]) by mouf.net (8.14.5/8.14.5) with ESMTP id s942rM19030466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 4 Oct 2014 02:53:27 GMT (envelope-from swills@mouf.net) Received: (from swills@localhost) by mouf.net (8.14.5/8.14.5/Submit) id s942rMmg030465; Sat, 4 Oct 2014 02:53:22 GMT (envelope-from swills) Date: Sat, 4 Oct 2014 02:53:22 +0000 From: Steve Wills To: Craig Rodrigues Subject: Re: Integrating pkg test results into Jenkins Message-ID: <20141004025319.GF10488@mouf.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Sat, 04 Oct 2014 02:53:27 +0000 (UTC) X-Spam-Status: No, score=0.0 required=4.5 tests=HEADER_FROM_DIFFERENT_DOMAINS autolearn=unavailable autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mouf.net X-Virus-Scanned: clamav-milter 0.98.3 at mouf.net X-Virus-Status: Clean Cc: "freebsd-testing@freebsd.org" , freebsd-pkg@freebsd.org X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Oct 2014 02:53:30 -0000 On Thu, Oct 02, 2014 at 01:22:55AM -0700, Craig Rodrigues wrote: > Hi, > > I notice that at http://jenkins.mouf.net/job/pkg/ you are using kyua to > test pkg. > > Instead of producing an HTML page of the test results, you may wish > to integrate the output of the tests directly into Jenkins. > > You can do this by: > > (1) In your Jenkins job's Build section, add this to the end: > > set +e > # You don't want the job to abort here if kyua returns > # non-zero status due to any test failurs > kyua test > kyua_status=$? > set -e > > kyua report-junit --output=$WORKSPACE/test-report.xml > exit $kyua_status > > (2) In your Jenkins job's Post-Build Actions, add: > > "Publish JUnit test result report" > > "Test Report XMLs" -> test-report.xml > > > The end result is quite nice, and looks like this: > > https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport/ Thanks for the suggestion, results are here: http://jenkins.mouf.net/job/pkg/lastCompletedBuild/testReport/ Steve From owner-freebsd-testing@FreeBSD.ORG Sat Oct 4 09:29:56 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 89ED9249 for ; Sat, 4 Oct 2014 09:29:56 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 71677A11 for ; Sat, 4 Oct 2014 09:29:56 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s949TudJ076339 for ; Sat, 4 Oct 2014 09:29:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-testing@freebsd.org Subject: [Bug 193499] [tests] usr.bin/yacc/err_syntax27.error failures with the latest kyua Date: Sat, 04 Oct 2014 09:29:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rodrigc@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-testing@freebsd.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Oct 2014 09:29:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499 --- Comment #5 from Craig Rodrigues --- Here's the stack trace I got: (gdb) where #0 reader () at /builds/FreeBSD_HEAD/usr.bin/yacc/../../contrib/byacc/reader.c:681 #1 0x00000000004053c9 in main (argc=, argv=) at /builds/FreeBSD_HEAD/usr.bin/yacc/../../contrib/byacc/main.c:692 (gdb) l 676 { 677 if (c == '\0') 678 missing_brace(); 679 if (c == EOF) 680 unexpected_EOF(); 681 buf[i] = (char)c; 682 } 683 684 if (i == 0) 685 goto out; -- You are receiving this mail because: You are the assignee for the bug.