From patchwork Wed Jan 20 08:58:23 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Daniel Vetter X-Patchwork-Id: 8070021 Return-Path: X-Original-To: patchwork-intel-gfx@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork1.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.136]) by patchwork1.web.kernel.org (Postfix) with ESMTP id 9BC039F6FA for ; Wed, 20 Jan 2016 08:58:27 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id CA431203DC for ; Wed, 20 Jan 2016 08:58:26 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) by mail.kernel.org (Postfix) with ESMTP id 782F3203A9 for ; Wed, 20 Jan 2016 08:58:25 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id B171D6E157; Wed, 20 Jan 2016 00:58:24 -0800 (PST) X-Original-To: intel-gfx@lists.freedesktop.org Delivered-To: intel-gfx@lists.freedesktop.org Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by gabe.freedesktop.org (Postfix) with ESMTPS id 5DDB86E157 for ; Wed, 20 Jan 2016 00:58:23 -0800 (PST) Received: by mail-wm0-f53.google.com with SMTP id r129so121846599wmr.0 for ; Wed, 20 Jan 2016 00:58:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=from:to:cc:subject:date:message-id; bh=pp5CII6tmce8CoN4FLEnmleQKbMOHU55Zu1pDf7xJEI=; b=VlOBQoSm4kO3YOxKQ3eELkVrEjnShRRDJESKAB5j23Li17CX3rra4SDivi9lvp+65u fzTf3AyWRnWKx8zeD5/7tP1K2IqqdfF4Y6A/AV+fgYOg5NfGBc6kwq94bYh8ARtqc8dp UplZy0uypqC4lELV7wso8bbMArw5svOa4xef4= 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; bh=pp5CII6tmce8CoN4FLEnmleQKbMOHU55Zu1pDf7xJEI=; b=QplOZFEbUzaG1W0YIoboNgaH+9xp3D8kzNQuRW57puxZxT6uM4qp+Iu4dJPEP1hkqa Ye3bzIBNlcrlzbOhWMSTOKtDztRyotR+B2ar9UpOL9Y7SFErxr5odrAfFSkEVGVEWo0J oR4CuqjqGp5Ds3Vp/yHPexM4XpUMs+1v+8NFjhdDCtLdAMqJRgKQ9oaZ5a25IW7PCByQ 0O6SiPkYYOfgSoN2IvQaf56tXNu5Xs2qtUq3WUs5Z/YJBZd1NMBN1L4U5G8VM8XQKVZn nnTm52yel/CiFiLADjPDzsaWiHB+K6sUD2wYc3Zxdw5CsaEnwJC6TvMYq7S5jjI/g+Ot SCbQ== X-Gm-Message-State: AG10YORonLx7OXd2DR4O/Q7KMRHVWFNLjUvocIOmKCblZmObUQhzkuVhBIYmWQnD+NKeoA== X-Received: by 10.194.104.38 with SMTP id gb6mr19073788wjb.22.1453280301751; Wed, 20 Jan 2016 00:58:21 -0800 (PST) Received: from phenom.ffwll.local ([2a02:168:56c9:0:22cf:30ff:fe4c:37d6]) by smtp.gmail.com with ESMTPSA id x6sm32047107wje.38.2016.01.20.00.58.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 20 Jan 2016 00:58:21 -0800 (PST) From: Daniel Vetter To: Intel Graphics Development Date: Wed, 20 Jan 2016 09:58:23 +0100 Message-Id: <1453280303-14179-1-git-send-email-daniel.vetter@ffwll.ch> X-Mailer: git-send-email 2.7.0.rc3 Cc: Daniel Vetter , Daniel Vetter Subject: [Intel-gfx] [PATCH] drm-intel: document that patches need to pass BAT 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: , MIME-Version: 1.0 Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Currently CI servers still push test results to internal servers, and that's why we right now can't document this all properly in public. Meanwhile just add a basic tl;dr section as a placeholder. Acked-by: Jani Nikula Signed-off-by: Daniel Vetter --- drm-intel.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/drm-intel.rst b/drm-intel.rst index 7871544a760f..cf58d64af1aa 100644 --- a/drm-intel.rst +++ b/drm-intel.rst @@ -390,6 +390,22 @@ On Confidence, Complexity, and Transparency you have involved enough people to feel comfortable if the justification for the commit is questioned afterwards. +* Make sure pre-merge testing is completed successfully. + + +Pre-Merge Testing +----------------- + +Our CI infrastructure is being built up and currently requirements for pre-merge +testing are fairly simple: + +* All patches must past IGT Basic Acceptance Tests (BAT) on all the CI machines + without causing regressions. The CI bots will send results to intel-gfx for + any patches tracked by patchwork. Check CI failures and make sure any sporadic + failures are a) pre-existing b) tracked in bugzilla. If there's anything + dubious that you can't track down to pre-existing&tracked issues please don't + push, but instead figure out what's going on. + Tooling =======