From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Auld, Matthew" <matthew.auld@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Latvala, Petri" <petri.latvala@intel.com>
Subject: Re: [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v2,1/4] drm/i915: don't call free_mmap_offset when purging
Date: Thu, 6 Jan 2022 19:17:21 +0000 [thread overview]
Message-ID: <42a2fa3a831c49f4b6c6a513db8fb013@intel.com> (raw)
In-Reply-To: <590572a8-b490-5516-11ab-5cda572eff73@intel.com>
I believe that's because of missing machine
Missing (7): bat-dg1-6 bat-dg1-5 fi-bsw-cyan bat-adlp-6 bat-rpls-1 fi-bdw-samus bat-jsl-1
Looks like DG1 results were not used while the report is generated. Good that you checked the full logs.
+@Latvala, Petri
Lakshmi.
-----Original Message-----
From: Auld, Matthew <matthew.auld@intel.com>
Sent: Thursday, January 6, 2022 10:07 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✓ Fi.CI.BAT: success for series starting with [v2,1/4] drm/i915: don't call free_mmap_offset when purging
Lakshmi, any idea why this reports as success? Clicking on the "See full logs" for BAT there is a clear new failure on DG1 in one of the selftests, which is caused by this series. It also doesn't appear in the issues hit below.
On 06/01/2022 12:32, Patchwork wrote:
> *Patch Details*
> *Series:* series starting with [v2,1/4] drm/i915: don't call
> free_mmap_offset when purging
> *URL:* https://patchwork.freedesktop.org/series/98548/
> <https://patchwork.freedesktop.org/series/98548/>
> *State:* success
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/index.html>
>
>
> CI Bug Log - changes from CI_DRM_11052 -> Patchwork_21930
>
>
> Summary
>
> *SUCCESS*
>
> No regressions found.
>
> External URL:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/index.html
>
>
> Participating hosts (44 -> 37)
>
> Missing (7): bat-dg1-6 bat-dg1-5 fi-bsw-cyan bat-adlp-6 bat-rpls-1
> fi-bdw-samus bat-jsl-1
>
>
> Known issues
>
> Here are the changes found in Patchwork_21930 that come from known issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@amdgpu/amd_basic@semaphore:
>
> o fi-bdw-5557u: NOTRUN -> SKIP
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-bdw-5557u/igt@amdgpu/amd_basic@semaphore.html>
> (fdo#109271
> <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +31
> similar issues
> *
>
> igt@amdgpu/amd_cs_nop@sync-compute0:
>
> o fi-kbl-soraka: NOTRUN -> SKIP
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-kbl-soraka/igt@amdgpu/amd_cs_nop@sync-compute0.html>
> (fdo#109271
> <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +6
> similar issues
> *
>
> igt@amdgpu/amd_prime@i915-to-amd:
>
> o fi-snb-2520m: NOTRUN -> SKIP
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-snb-2520m/igt@amdgpu/amd_prime@i915-to-amd.html>
> (fdo#109271
> <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +17
> similar issues
> *
>
> igt@gem_exec_suspend@basic-s3:
>
> o fi-skl-6600u: NOTRUN -> INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-skl-6600u/igt@gem_exec_suspend@basic-s3.html>
> (i915#4547 <https://gitlab.freedesktop.org/drm/intel/issues/4547>)
> *
>
> igt@kms_chamelium@dp-crc-fast:
>
> o fi-bdw-5557u: NOTRUN -> SKIP
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-bdw-5557u/igt@kms_chamelium@dp-crc-fast.html>
> (fdo#109271
> <https://bugs.freedesktop.org/show_bug.cgi?id=109271> /
> fdo#111827
> <https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +8
> similar issues
>
>
> Possible fixes
>
> *
>
> igt@gem_exec_suspend@basic-s3@smem:
>
> o fi-icl-u2: FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11052/fi-icl-u2/igt@gem_exec_suspend@basic-s3@smem.html>
> (i915#1888
> <https://gitlab.freedesktop.org/drm/intel/issues/1888>) -> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-icl-u2/igt@gem_exec_suspend@basic-s3@smem.html>
> *
>
> igt@i915_selftest@live@gt_contexts:
>
> o fi-snb-2520m: DMESG-FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11052/fi-snb-2520m/igt@i915_selftest@live@gt_contexts.html>
> (i915#4610
> <https://gitlab.freedesktop.org/drm/intel/issues/4610>) -> PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-snb-2520m
> /igt@i915_selftest@live@gt_contexts.html>
>
>
> Build changes
>
> * Linux: CI_DRM_11052 -> Patchwork_21930
>
> CI-20190529: 20190529
> CI_DRM_11052: 5926026a36a658f615b8a5aaa74a90a2a3c5e6c5 @
> git://anongit.freedesktop.org/gfx-ci/linux
> IGT_6324: 6e009504d5f7cc39866191e4bff813a4512c3e9b @
> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> Patchwork_21930: be0926fec2d647c269ce85910715a088c17397ef @
> git://anongit.freedesktop.org/gfx-ci/linux
>
> == Linux commits ==
>
> be0926fec2d6 drm/i915/ttm: ensure we unmap when purging e0c70169a2fd
> drm/i915/ttm: add unmap_virtual callback
> c3ae17de8264 drm/i915/ttm: only fault WILLNEED objects ce8969fa161a
> drm/i915: don't call free_mmap_offset when purging
>
next prev parent reply other threads:[~2022-01-06 19:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 11:20 [Intel-gfx] [PATCH v2 1/4] drm/i915: don't call free_mmap_offset when purging Matthew Auld
2022-01-06 11:20 ` [Intel-gfx] [PATCH v2 2/4] drm/i915/ttm: only fault WILLNEED objects Matthew Auld
2022-01-06 11:20 ` [Intel-gfx] [PATCH v2 3/4] drm/i915/ttm: add unmap_virtual callback Matthew Auld
2022-01-06 11:20 ` [Intel-gfx] [PATCH v2 4/4] drm/i915/ttm: ensure we unmap when purging Matthew Auld
2022-01-06 12:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/4] drm/i915: don't call free_mmap_offset " Patchwork
2022-01-06 12:15 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-06 12:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-06 18:07 ` Matthew Auld
2022-01-06 19:17 ` Vudum, Lakshminarayana [this message]
2022-01-07 13:51 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42a2fa3a831c49f4b6c6a513db8fb013@intel.com \
--to=lakshminarayana.vudum@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=petri.latvala@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox