From patchwork Fri Oct 7 07:06:31 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Daniel Vetter X-Patchwork-Id: 9365719 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id B1EEC60752 for ; Fri, 7 Oct 2016 07:06:43 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id A37AB29334 for ; Fri, 7 Oct 2016 07:06:43 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 9881A29351; Fri, 7 Oct 2016 07:06:43 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=2.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_MED,T_DKIM_INVALID autolearn=ham version=3.3.1 Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id 4BD8129334 for ; Fri, 7 Oct 2016 07:06:43 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 800B16EAFB; Fri, 7 Oct 2016 07:06:41 +0000 (UTC) X-Original-To: intel-gfx@lists.freedesktop.org Delivered-To: intel-gfx@lists.freedesktop.org Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) by gabe.freedesktop.org (Postfix) with ESMTPS id D6AAC6EAFB for ; Fri, 7 Oct 2016 07:06:39 +0000 (UTC) Received: by mail-wm0-x243.google.com with SMTP id f193so1456992wmg.2 for ; Fri, 07 Oct 2016 00:06:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=ohCSofHwUQjbR2bE21h8roeHqenqT96n+9BiUwsEeL4=; b=K/5kThOiHOf10UxxA615oWNhxBrOvHeCW0YYi0HJzUcCUx9z0u6CWqR+INWCX9UtQ7 gVFTkWPAHXBPIsxhYD48zdE1ztWdXbbFdOy3F/8bH/cG/1lI2FWb0HXzpI5xsTOBrtaz QjA74OWjoek0PkIDSyDPQSQGckHobDZQTTLC4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=ohCSofHwUQjbR2bE21h8roeHqenqT96n+9BiUwsEeL4=; b=DmAE8sTH1JvzJSX+bBkK+VVwX4+rXBbUB2vIY4ZtWz2LBZWI9Q7N5CGcs4smXoZI/4 hB8/anz3bVgR82PSywpDlh0Osp0im0RoLqKDZWkg5kPbmVqqShXr3F1vKLPa+q/POHHF 574vUk3pzcW3MKXrpabY5UhhJzCTiThMRI6npgCPrvVt6yViIZSsffNyRH7BQwRBK7v7 aAw/v1UU3GDFYcmmNZpKN4pFXpAn+r4jKos98maAzio68kiZAlx3Q7NL5JNxxv0etXxB W68k0GvhY+j3K4hhpk2ltBdlUWWvsUupghm4P2A91rwskRtSiRNFAtJIzMHMSaKi9IPu wuBA== X-Gm-Message-State: AA6/9RkDSDSjfhVaJtVCpo2HQV5VAV0f7VWWrLGenkGDRLM+BqbXcR4u3dbRjtXihBERcw== X-Received: by 10.28.8.139 with SMTP id 133mr4647563wmi.80.1475823998125; Fri, 07 Oct 2016 00:06:38 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:56b5:0:ac27:b86c:7764:9429]) by smtp.gmail.com with ESMTPSA id y4sm1504266wmy.22.2016.10.07.00.06.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Oct 2016 00:06:36 -0700 (PDT) From: Daniel Vetter To: Intel Graphics Development Date: Fri, 7 Oct 2016 09:06:31 +0200 Message-Id: <20161007070631.732-1-daniel.vetter@ffwll.ch> X-Mailer: git-send-email 2.9.3 MIME-Version: 1.0 Cc: jari.tahvanainen@intel.com, piglit discussion list , Daniel Vetter , Daniel Vetter Subject: [Intel-gfx] [PATCH] tests/igt: dmesg noise is a kernel failure X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" X-Virus-Scanned: ClamAV using ClamSMTP At least when testing the kernel. In normal programs pretty much all the dmesg noise would simply be replaced by debug asserts, but in the kernel we try rely hard to not fall over minor inconsistencies. Still for CI purposes there's not really a difference, hence don't treat it as such. Motivated since once again I've seen a statistics where this was split up, and then a reduction of "failures" (but in reality just trading them in for more "warnings") praised as success. v2: Clamp to "dmesg-fail" to keep dmesg noise easily identifiable (Ville). Cc: Chris Wilson Cc: Ville Syrjälä Acked-by: Dylan Baker Cc: jari.tahvanainen@intel.com Cc: Petri Latvala Signed-off-by: Daniel Vetter --- tests/igt.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tests/igt.py b/tests/igt.py index 7ebb03646b50..21e55e115654 100644 --- a/tests/igt.py +++ b/tests/igt.py @@ -123,6 +123,10 @@ class IGTTest(Test): else: self.result.result = 'fail' + # all dmesg noise is considered a test failure when testing the kernel + if self.result.dmesg + self.result.result = 'dmesg-fail' + def list_tests(listname): """Parse igt test list and return them as a list."""