From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: ✗ CI.BAT: failure for TTM shrinker helpers and xe buffer object shrinker (rev10)
Date: Mon, 21 Oct 2024 12:50:24 +0200 [thread overview]
Message-ID: <525c1c97dc6d0c5a0118356854825ef74e6346e9.camel@linux.intel.com> (raw)
In-Reply-To: <ZxVTnTQOl4NSf2i7@DUT025-TGLU.fm.intel.com>
On Sun, 2024-10-20 at 19:01 +0000, Matthew Brost wrote:
> On Wed, Oct 16, 2024 at 11:59:32AM +0000, Patchwork wrote:
> > Patch Details
> >
> > Series: TTM shrinker helpers and xe buffer object shrinker
> > (rev10)
> > URL: [1]https://patchwork.freedesktop.org/series/131815/
> > State: failure
> > Details:
> >
> > [2]https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-131815v10/index.
> > html
> >
> > CI Bug Log - changes from xe-2072-
> > 12e4970af1ecdeb76e94df2daf51a9c3d6b9f519_BAT
> > -> xe-pw-131815v10_BAT
> >
> > Summary
> >
> > FAILURE
> >
> > Serious unknown changes coming with xe-pw-131815v10_BAT
> > absolutely need
> > to be
> > verified manually.
> >
> > If you think the reported changes have nothing to do with the
> > changes
> > introduced in xe-pw-131815v10_BAT, please notify your bug team
> > (I915-ci-infra@lists.freedesktop.org) to allow them
> > to document this new failure mode, which will reduce false
> > positives in
> > CI.
> >
> > Participating hosts (9 -> 9)
> >
> > No changes in participating hosts
> >
> > Possible new issues
> >
> > Here are the unknown changes that may have been introduced in
> > xe-pw-131815v10_BAT:
> >
> > IGT changes
> >
> > Possible regressions
> >
> > * igt@xe_live_ktest@xe_bo:
> > + bat-adlp-vf: [3]PASS -> [4]INCOMPLETE +1 other test
> > incomplete
> > + bat-lnl-1: [5]PASS -> [6]INCOMPLETE +1 other test
> > incomplete
> > * igt@xe_live_ktest@xe_bo@xe_bo_shrink_kunit:
> > + bat-lnl-2: [7]PASS -> [8]INCOMPLETE +1 other test
> > incomplete
>
> These look related. Any idea what these are about? Should I continue
> with my review or do you think another rev is needed?
Please continue. I'll investigate those, but I think they are related
to igt test duration timeouts. These tests execute for a very long
time, and it's hard to come up with a bulletproof way to shorten the
execution time.
/Thomas
>
> Matt
>
> >
> > Known issues
> >
> > Here are the changes found in xe-pw-131815v10_BAT that come from
> > known
> > issues:
> >
> > IGT changes
> >
> > Issues hit
> >
> > * igt@xe_live_ktest@xe_bo@xe_bo_shrink_kunit:
> > + bat-adlp-7: [9]PASS -> [10]INCOMPLETE ([11]Intel
> > XE#2874) +1
> > other test incomplete
> >
> > Possible fixes
> >
> > * igt@kms_frontbuffer_tracking@basic:
> > + bat-adlp-7: [12]FAIL ([13]Intel XE#1861) -> [14]PASS
> >
> > Warnings
> >
> > *
> > igt@xe_exec_compute_mode@twice-bindexecqueue-userptr-invalidate:
> > + bat-lnl-1: [15]DMESG-FAIL ([16]Intel XE#2687) ->
> > [17]FAIL
> > ([18]Intel XE#2754)
> >
> > Build changes
> >
> > * IGT: IGT_8076 -> IGT_8077
> > * Linux: xe-2072-12e4970af1ecdeb76e94df2daf51a9c3d6b9f519 ->
> > xe-pw-131815v10
> >
> > IGT_8076: e511df10a1201d0d83c03ccbcabc3d57191e5f8e @
> > https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> > IGT_8077: 42f9e9702f74a4993318adea936baaa186084689 @
> > https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> > xe-2072-12e4970af1ecdeb76e94df2daf51a9c3d6b9f519:
> > 12e4970af1ecdeb76e94df2daf51a9c3d6b9f519
> > xe-pw-131815v10: 131815v10
> >
> > References
> >
> > 1. https://patchwork.freedesktop.org/series/131815/
> > 2.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-131815v10/index.html
> > 3.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-2072-12e4970af1ecdeb76e94df2daf51a9c3d6b9f519/bat-adlp-vf/igt@xe_live_ktest@xe_bo.html
> > 4.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-131815v10/bat-adlp-vf/igt@xe_live_ktest@xe_bo.html
> > 5.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-2072-12e4970af1ecdeb76e94df2daf51a9c3d6b9f519/bat-lnl-1/igt@xe_live_ktest@xe_bo.html
> > 6.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-131815v10/bat-lnl-1/igt@xe_live_ktest@xe_bo.html
> > 7.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-2072-12e4970af1ecdeb76e94df2daf51a9c3d6b9f519/bat-lnl-2/igt@xe_live_ktest@xe_bo@xe_bo_shrink_kunit.html
> > 8.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-131815v10/bat-lnl-2/igt@xe_live_ktest@xe_bo@xe_bo_shrink_kunit.html
> > 9.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-2072-12e4970af1ecdeb76e94df2daf51a9c3d6b9f519/bat-adlp-7/igt@xe_live_ktest@xe_bo@xe_bo_shrink_kunit.html
> > 10.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-131815v10/bat-adlp-7/igt@xe_live_ktest@xe_bo@xe_bo_shrink_kunit.html
> > 11. https://gitlab.freedesktop.org/drm/xe/kernel/issues/2874
> > 12.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-2072-12e4970af1ecdeb76e94df2daf51a9c3d6b9f519/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
> > 13. https://gitlab.freedesktop.org/drm/xe/kernel/issues/1861
> > 14.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-131815v10/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
> > 15.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-2072-12e4970af1ecdeb76e94df2daf51a9c3d6b9f519/bat-lnl-1/igt@xe_exec_compute_mode@twice-bindexecqueue-userptr-invalidate.html
> > 16. https://gitlab.freedesktop.org/drm/xe/kernel/issues/2687
> > 17.
> > https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-131815v10/bat-lnl-1/igt@xe_exec_compute_mode@twice-bindexecqueue-userptr-invalidate.html
> > 18. https://gitlab.freedesktop.org/drm/xe/kernel/issues/2754
next prev parent reply other threads:[~2024-10-21 10:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 8:55 [PATCH v11 0/8] TTM shrinker helpers and xe buffer object shrinker Thomas Hellström
2024-10-16 8:55 ` [PATCH v11 1/8] drm/ttm: Balance ttm_resource_cursor_init() and ttm_resource_cursor_fini() Thomas Hellström
2024-10-16 8:55 ` [PATCH v11 2/8] drm/ttm: Add a virtual base class for graphics memory backup Thomas Hellström
2024-11-08 14:32 ` Christian König
2024-11-11 14:38 ` Thomas Hellström
2024-11-11 16:13 ` Christian König
2024-10-16 8:55 ` [PATCH v11 3/8] drm/ttm/pool: Provide a helper to shrink pages Thomas Hellström
2024-10-20 18:38 ` Matthew Brost
2024-10-16 8:55 ` [PATCH v11 4/8] drm/ttm: Use fault-injection to test error paths Thomas Hellström
2024-10-16 8:55 ` [PATCH v11 5/8] drm/ttm: Add a macro to perform LRU iteration Thomas Hellström
2024-10-20 18:54 ` Matthew Brost
2024-10-20 18:57 ` Matthew Brost
2024-10-16 8:55 ` [PATCH v11 6/8] drm/ttm: Add helpers for shrinking Thomas Hellström
2024-10-21 21:37 ` Matthew Brost
2024-10-16 8:55 ` [PATCH v11 7/8] drm/xe: Add a shrinker for xe bos Thomas Hellström
2024-10-24 17:00 ` Matthew Brost
2024-10-16 8:55 ` [PATCH v11 8/8] drm/xe: Increase the XE_PL_TT watermark Thomas Hellström
2024-10-16 10:56 ` ✓ CI.Patch_applied: success for TTM shrinker helpers and xe buffer object shrinker (rev10) Patchwork
2024-10-16 10:57 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-16 10:58 ` ✓ CI.KUnit: success " Patchwork
2024-10-16 11:09 ` ✓ CI.Build: " Patchwork
2024-10-16 11:11 ` ✓ CI.Hooks: " Patchwork
2024-10-16 11:13 ` ✗ CI.checksparse: warning " Patchwork
2024-10-16 11:59 ` ✗ CI.BAT: failure " Patchwork
2024-10-20 19:01 ` Matthew Brost
2024-10-21 10:50 ` Thomas Hellström [this message]
2024-10-17 1:10 ` ✗ CI.FULL: " 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=525c1c97dc6d0c5a0118356854825ef74e6346e9.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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