From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C659EC433FE for ; Fri, 3 Sep 2021 12:58:33 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 906CD60249 for ; Fri, 3 Sep 2021 12:58:33 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 906CD60249 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 4158F6E88B; Fri, 3 Sep 2021 12:58:33 +0000 (UTC) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by gabe.freedesktop.org (Postfix) with ESMTPS id 2253C6E88B for ; Fri, 3 Sep 2021 12:58:32 +0000 (UTC) X-IronPort-AV: E=McAfee;i="6200,9189,10095"; a="219474722" X-IronPort-AV: E=Sophos;i="5.85,265,1624345200"; d="scan'208";a="219474722" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Sep 2021 05:58:11 -0700 X-IronPort-AV: E=Sophos;i="5.85,265,1624345200"; d="scan'208";a="692224434" Received: from thrakatuluk.fi.intel.com (HELO thrakatuluk) ([10.237.68.154]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Sep 2021 05:58:08 -0700 Received: from platvala by thrakatuluk with local (Exim 4.94) (envelope-from ) id 1mM8oh-0005do-LB; Fri, 03 Sep 2021 16:01:11 +0300 Date: Fri, 3 Sep 2021 16:01:11 +0300 From: Petri Latvala To: Tvrtko Ursulin Cc: jim.cromie@gmail.com, Intel Graphics Development , Jigar Bhatt , Anshuman Gupta Message-ID: References: <20210831202133.2165222-1-jim.cromie@gmail.com> <163045309469.10657.6449873390681387525@emeril.freedesktop.org> <1f670a6b-af77-0e07-880e-57b1e28bfc7b@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1f670a6b-af77-0e07-880e-57b1e28bfc7b@linux.intel.com> X-Patchwork-Hint: comment Subject: Re: [Intel-gfx] =?utf-8?b?4pyXIEZpLkNJLklHVDogZmFpbHVyZSBmb3IgdXNl?= =?utf-8?q?_DYNAMIC=5FDEBUG_to_implement_DRM=2Edebug_=28rev2=29?= X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 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" On Fri, Sep 03, 2021 at 12:29:51PM +0100, Tvrtko Ursulin wrote: > > On 03/09/2021 01:31, jim.cromie@gmail.com wrote: > > > > > > On Tue, Aug 31, 2021 at 5:38 PM Patchwork > > > > wrote: > > > > __ > > *Patch Details* > > *Series:* use DYNAMIC_DEBUG to implement DRM.debug (rev2) > > *URL:* https://patchwork.freedesktop.org/series/93914/ > > > > *State:* failure > > *Details:* > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20931/index.html > > > > > > > > CI Bug Log - changes from CI_DRM_10541_full -> Patchwork_20931_full > > > > > > Summary > > > > *FAILURE* > > > > Serious unknown changes coming with Patchwork_20931_full absolutely > > need to be > > verified manually. > > > > If you think the reported changes have nothing to do with the changes > > introduced in Patchwork_20931_full, please notify your bug team to > > allow them > > to document this new failure mode, which will reduce false positives > > in CI. > > > > > > hi Team ! > > > > I think I need a bit of orientation. > > > > > > Possible new issues > > > > Here are the unknown changes that may have been introduced in > > Patchwork_20931_full: > > > > > > IGT changes > > > > > > Possible regressions > > > > * igt@gem_exec_schedule@u-submit-golden-slice@vcs0: > > o shard-skl: NOTRUN -> INCOMPLETE > > > > > > > > Warnings > > > > * igt@i915_pm_dc@dc9-dpms: > > o shard-skl: SKIP > > > > ([fdo#109271]) -> FAIL > > > > > > > > > > Im assuming the FAIL is the sticking point, > > Both INCOMPLETE and FAIL will cause a failure to be declared, but in this case it looks to me this series is not at fault. > > 1) > > The gem_exec_schedule failure looks like a test runner timeout issue (and apparently test does not handle well running the the fence timeout enabled). > > @Petri - does the below look like IGT runner running our of time budget for the test run? Would it log > > [1051.943629] [114/138] ( 11s left) gem_exec_schedule (u-submit-golden-slice) > Starting subtest: u-submit-golden-slice > Starting dynamic subtest: rcs0 > Dynamic subtest rcs0: SUCCESS (80.175s) > Starting dynamic subtest: bcs0 > Dynamic subtest bcs0: SUCCESS (80.195s) > Starting dynamic subtest: vcs0 > Dynamic subtest vcs0: SUCCESS (80.243s) > Starting dynamic subtest: vecs0 > > Interesting part is that according to dmesg it never got to the vecs0 dynamic subtest - any idea what happened there? Yep, we ran out of time. We still had 11 seconds left to execute something but then that test took centuries. > > 2) > > I915_pm_dc I'd say you just gotten unlucky that test went from always skipping on SKL to trying to run it and then it failed. But I don't know enough about the test to tell you why. Adding Jigar and Anshuman as test author and reviewer who might be able to shed some light here. > > Regards, > > Tvrtko > > > I found code that seemed to be relevant > > > > [jimc@frodo igt-ci-tags.git]$ git remote -v > > origin https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags.git > > (fetch) > > origin https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags.git > > (push) > > > > I built it, got an error, threw that to google, > > found a patch on i-g-t from > > commit 1ff3e5ae99ceb66d2926d58635d0379ce971065a (HEAD -> master) > > Author: Lyude Paul > > > Date:   Mon Apr 15 14:57:23 2019 -0400 > > > > and applied it > > it fixed the one problem > > > > then I looked at previous head > > > > commit f052e49a43cc9704ea5f240df15dd9d3dfed68ab (origin/master, origin/HEAD) > > Author: Simon Ser > > > Date:   Wed Apr 24 19:15:26 2019 +0300 > > > > It sure seems that tree is stale. That tree's master ref does not get updated. It's only for storing tags. That test result comparison was too long to fit into patchwork so the build information at the bottom is missing, but the BAT results have it: IGT_6193: 080869f804cb86b25a38889e5ce9a870571cd8c4 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git -- Petri Latvala