Received: by 2002:a05:6358:c692:b0:131:369:b2a3 with SMTP id fe18csp4610774rwb; Mon, 31 Jul 2023 09:21:28 -0700 (PDT) X-Google-Smtp-Source: APBJJlEYmvH7WKbLGUd+IzG3qZiRGftpkvThVRBPf0kg8bimKjSUNtd2IwzuJi/Rz9bTw6QmK64U X-Received: by 2002:a05:6402:185a:b0:522:5548:f357 with SMTP id v26-20020a056402185a00b005225548f357mr319747edy.28.1690820488618; Mon, 31 Jul 2023 09:21:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690820488; cv=none; d=google.com; s=arc-20160816; b=gbCPso70pMuuRrv+RfNrB8l1reDwQ09r7ipw3C+oP8WoHN7TYH9737u9fjtRdopLYc TaZcX2cSdWtN4AwnKh+qdz5NMorZkYamn+wjXU6Glfbzwf6BDTnwQZSijkZNU1AuYhIN A2BTENEZEiVQ8IFDs8L20eTseWRBf79xPl2yuc2iQbKCEIzMLDHgU0aFURri9c4KaEIg kdb7c2/8w25SP9x+QMHmnzF/LtYIcvftG6zLCN3ipfal/VHz/vrHUnLMIMJqNQYwA+WH hTMdvqjZ1N7khGfCU55dgdk0reDfl9Q+o0Fo7c24gmWuwAgIhHCQaUh/tR/bg/JFOTIg eUEw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=fAPrkbK19s/j5Zx9BvuYAYuY534VPCFu5UMSEPN+FAE=; fh=88fjKKGTLJ/qBaK2kKoX+lMdJHZ16jXwept4bOU2Hzs=; b=yHrL2xvakF/qAcRjXVlCyAjLbN1PHp333Q3kGh0bEeueBzaMqUZox5lXXsy6KXpBAy FUaI5AikCAvPXdvz5LjrzQahtMJ9L/cm8RdbanvyNNxUrxaAS4JYIUNjMHuHuLvYhYgj wLehOJMtzLvPvBYF3rW1cy5vMiejDbtxLVc72C9MbfquWe9l2q4cPuRjm0uZULlLGUeZ CB377ar49vTDIPijKoe8Zq9s2o7AAhrJMpYS5iOy6N2Tj8s0DUliZrcC+VNR/ssy7ZIq +emHDlePKtTh5IQ1i1nebNOCwZEbxG7lAfQ9h0apE+1mIsZDzm87SESOyT/lXjbDa5Hd ts2g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=ONefshDk; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u15-20020aa7d88f000000b005221dcc6470si2458338edq.591.2023.07.31.09.21.03; Mon, 31 Jul 2023 09:21:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=ONefshDk; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229537AbjGaOvc (ORCPT + 99 others); Mon, 31 Jul 2023 10:51:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54194 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233131AbjGaOvZ (ORCPT ); Mon, 31 Jul 2023 10:51:25 -0400 Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1BA4CE78; Mon, 31 Jul 2023 07:51:21 -0700 (PDT) Received: by mail-wr1-x434.google.com with SMTP id ffacd0b85a97d-314417861b9so3867611f8f.0; Mon, 31 Jul 2023 07:51:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690815079; x=1691419879; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=fAPrkbK19s/j5Zx9BvuYAYuY534VPCFu5UMSEPN+FAE=; b=ONefshDkN1jXMyg0wZ8QEmmAPXYcp3mA7Y4rLHbZ0B/sSm8FGewPffgqtdxTL/X1iT AtnNYgJ+osFjNol3DgEwCoRMsRzED9sEjdYo+XNB6jA/vpUD06z0WPGVpFwk6veFO9OU ibatrDvsrl3GB3m2uFuEY1sklgbBbV+M1ieeB/BLXlqQriOZZEEhJRnlTc6k3zry1pGI 8gT4pqVcCYAqeSjkliWxyT6pMGXOg8y1USl58BKNqUR4FGu0Ju4rskBjkX0SaL4zQ9IR mABJjkmvgdQUqRb0sebjRifxOKcjyv4RmV6FD7aKFsKCahByl3oE/ln33nEvLUOnN/IR cPxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690815079; x=1691419879; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=fAPrkbK19s/j5Zx9BvuYAYuY534VPCFu5UMSEPN+FAE=; b=EdkSzJe4WXKljAkSuv6Tp5vkScZYwp2APQQ6e98Cr/gZ/TGLmYiADEgYwRNXnImXeB 1NBkZyx35/Es/EOuUmYt3U9hLimN4+Yc5BKYTmGNjyM4z4VPX33ICVxfTBZdjBPSExK5 aI25fSquP9JRudKjSGgt/ZSN/fJ4BHCNzws0v3t/n5cOUGB/mIOZcPRYp3VSBLpOHCwn FEnaYxwWPKh6ITwnpYuLVa1jrlqV/neqqikLm71217Q50+6c1xoOjnUOH6/q9plt/wun hxl+dPglZ9qA55tjUARp8AjL/MDVC33jOnxb+KmLZzauRqdlwabNhGt3eEcY5vwGCmGU NinQ== X-Gm-Message-State: ABy/qLZOx1f+WHqxdRaTwqlLiHDkGzooLPXnmuoe4RNYPNuS2RaAjfIv 4bl9IWyr9i/gJYvhcm83hoqFzTKxXCFEdjSi8D4= X-Received: by 2002:adf:e752:0:b0:314:3f98:a788 with SMTP id c18-20020adfe752000000b003143f98a788mr58676wrn.7.1690815079341; Mon, 31 Jul 2023 07:51:19 -0700 (PDT) MIME-Version: 1.0 References: <282e-64c7a800-77-46253680@38053863> In-Reply-To: <282e-64c7a800-77-46253680@38053863> From: Rob Clark Date: Mon, 31 Jul 2023 07:51:07 -0700 Message-ID: Subject: Re: [PATCH v10] drm: Add initial ci/ subdirectory To: Helen Mae Koike Fornazier Cc: Daniel Stone , emma@anholt.net, linux-doc@vger.kernel.org, david.heidelberg@collabora.com, dri-devel@lists.freedesktop.org, linux-amlogic@lists.infradead.org, jbrunet@baylibre.com, robdclark@google.com, corbet@lwn.net, khilman@baylibre.com, sergi.blanch.torne@collabora.com, gustavo.padovan@collabora.com, linux-rockchip@lists.infradead.org, daniels@collabora.com, martin.blumenstingl@googlemail.com, mripard@kernel.org, anholt@google.com, linux-mediatek@lists.infradead.org, robclark@freedesktop.org, matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org, angelogioacchino.delregno@collabora.com, neil.armstrong@linaro.org, guilherme.gallo@collabora.com, linux-kernel@vger.kernel.org, tzimmermann@suse.de, Dave Airlie , Daniel Vetter Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 31, 2023 at 5:25=E2=80=AFAM Helen Mae Koike Fornazier wrote: > > Hello all, > > Thanks for your comments. > > On Friday, July 28, 2023 11:37 -03, Rob Clark wrote= : > > > On Thu, Jul 27, 2023 at 10:26=E2=80=AFPM Daniel Stone wrote: > > > > > > On Thu, 27 Jul 2023 at 22:47, Rob Clark wrote: > > > > > I did run into a bit of a chicken vs. egg problem with testing th= e "in > > > > > tree" version (compared to earlier versions which kept most of th= e yml > > > > > and scripts in a separate tree), is that it actually requires thi= s > > > > > commit to exist in the branch you want to run CI on. My earlier > > > > > workaround of pulling the drm/ci commit in via > > > > > ${branchname}-external-fixes no longer works. > > > > > > > > After unwinding some more gitlab repo settings that were for the > > > > previous out-of-tree yml setup, I have this working. > > > > > > > > Tested-by: Rob Clark > > > > Acked-by: Rob Clark > > > > > > And it's also: > > > Acked-by: Daniel Stone > > > > > > It's been back and forth a few times by now and reviewed pretty > > > heavily by all the people who are across the CI details. I think the > > > next step is to answer all the workflow questions by actually getting > > > it into trees and using it in anger. There was some discussion about > > > whether this should come in from drm-misc, or the core DRM tree, or a > > > completely separate pull, but I'm not sure what the conclusion was ..= . > > > maintainers, thoughts? > > > > I'd prefer a separate pull, so that I could merge it into msm-next as > > well without having to pull in all of drm-misc > > Should we create a drm-ci ? I guess we can just wait and see how often it is that drm/ci updates need to be merged into multiple driver trees. Hopefully most of the drm/ci changes are just expectation file updates which should go via driver tree. Maybe i-g-t uprevs, if they have a lot of expectation changes would be something drivers would want to merge into their own tree? But I guess we can see how it goes. > > > > Possibly some other driver trees would like to do similar? > > > > BR, > > -R > > Also, please wait for v11, I have a few adjustments to make as pointer by > some comments, and also regarding xfails list and how the configs should > be organized (unless if you are fine merging this version and I can submi= t > the adjustments later). Ok BR, -R > Thanks, > Helen >