diff mbox

drm-intel: document that patches need to pass BAT

Message ID 1453280303-14179-1-git-send-email-daniel.vetter@ffwll.ch (mailing list archive)
State New, archived
Headers show

Commit Message

Daniel Vetter Jan. 20, 2016, 8:58 a.m. UTC 
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 <jani.nikula@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
 drm-intel.rst | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
diff mbox

Patch

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
 =======