* [PATCH 0/2] drm: revert some framebuffer API tests
@ 2024-09-17 17:43 Jani Nikula
2024-09-17 17:43 ` [PATCH 1/2] Revert "drm/tests: Add test for drm_framebuffer_free()" Jani Nikula
` (5 more replies)
0 siblings, 6 replies; 24+ messages in thread
From: Jani Nikula @ 2024-09-17 17:43 UTC (permalink / raw)
To: dri-devel
Cc: intel-gfx, jani.nikula, Carlos Eduardo Gallo Filho, Maxime Ripard,
Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson
The tests consistently trigger WARNs in drm_framebuffer code. I'm not
sure what the point is with type of belts and suspenders tests. The
warnings *are* the way to flag erroneous API usage.
Warnings in turn trigger failures in CI. Filtering the warnings are
error prone, and, crucially, would also filter actual errors in case the
kunit tests are not run.
I acknowledge there may be complex test cases where you'd end up
triggering warnings somewhere deep, but these are not it. These are
simple.
Revert the tests, back to the drawing board.
BR,
Jani.
Cc: Carlos Eduardo Gallo Filho <gcarlos@disroot.org>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>
Jani Nikula (2):
Revert "drm/tests: Add test for drm_framebuffer_free()"
Revert "drm/tests: Add test for drm_framebuffer_init()"
drivers/gpu/drm/drm_framebuffer.c | 1 -
drivers/gpu/drm/drm_mode_object.c | 1 -
drivers/gpu/drm/tests/drm_framebuffer_test.c | 134 -------------------
3 files changed, 136 deletions(-)
--
2.39.2
^ permalink raw reply [flat|nested] 24+ messages in thread* [PATCH 1/2] Revert "drm/tests: Add test for drm_framebuffer_free()" 2024-09-17 17:43 [PATCH 0/2] drm: revert some framebuffer API tests Jani Nikula @ 2024-09-17 17:43 ` Jani Nikula 2024-09-17 17:43 ` [PATCH 2/2] Revert "drm/tests: Add test for drm_framebuffer_init()" Jani Nikula ` (4 subsequent siblings) 5 siblings, 0 replies; 24+ messages in thread From: Jani Nikula @ 2024-09-17 17:43 UTC (permalink / raw) To: dri-devel Cc: intel-gfx, jani.nikula, Carlos Eduardo Gallo Filho, Maxime Ripard, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson This reverts commit d2194256049910d286cd6c308c2689df521d8842. Intel CI consistently hits a WARN in drm_framebuffer_free() with this test, because the fb->filp_head list is uninitialized. Link: https://lore.kernel.org/r/87plp7ex27.fsf@intel.com Fixes: d21942560499 ("drm/tests: Add test for drm_framebuffer_free()") Cc: Carlos Eduardo Gallo Filho <gcarlos@disroot.org> Cc: Maxime Ripard <mripard@kernel.org> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Cc: Thomas Zimmermann <tzimmermann@suse.de> Cc: Jeff Johnson <quic_jjohnson@quicinc.com> Signed-off-by: Jani Nikula <jani.nikula@intel.com> --- drivers/gpu/drm/drm_mode_object.c | 1 - drivers/gpu/drm/tests/drm_framebuffer_test.c | 50 -------------------- 2 files changed, 51 deletions(-) diff --git a/drivers/gpu/drm/drm_mode_object.c b/drivers/gpu/drm/drm_mode_object.c index e943205a2394..df4cc0e8e263 100644 --- a/drivers/gpu/drm/drm_mode_object.c +++ b/drivers/gpu/drm/drm_mode_object.c @@ -81,7 +81,6 @@ int drm_mode_object_add(struct drm_device *dev, { return __drm_mode_object_add(dev, obj, obj_type, true, NULL); } -EXPORT_SYMBOL_FOR_TESTS_ONLY(drm_mode_object_add); void drm_mode_object_register(struct drm_device *dev, struct drm_mode_object *obj) diff --git a/drivers/gpu/drm/tests/drm_framebuffer_test.c b/drivers/gpu/drm/tests/drm_framebuffer_test.c index 6ea04cc8f324..72314805839d 100644 --- a/drivers/gpu/drm/tests/drm_framebuffer_test.c +++ b/drivers/gpu/drm/tests/drm_framebuffer_test.c @@ -358,7 +358,6 @@ static const struct drm_framebuffer_test drm_framebuffer_create_cases[] = { struct drm_framebuffer_test_priv { struct drm_device dev; bool buffer_created; - bool buffer_freed; }; static struct drm_framebuffer *fb_create_mock(struct drm_device *dev, @@ -650,59 +649,10 @@ static void drm_test_framebuffer_init_dev_mismatch(struct kunit *test) KUNIT_EXPECT_EQ(test, ret, -EINVAL); } -static void destroy_free_mock(struct drm_framebuffer *fb) -{ - struct drm_framebuffer_test_priv *priv = container_of(fb->dev, typeof(*priv), dev); - - priv->buffer_freed = true; -} - -static struct drm_framebuffer_funcs framebuffer_funcs_free_mock = { - .destroy = destroy_free_mock, -}; - -/* - * In summary, the drm_framebuffer_free() function must implicitly call - * fb->funcs->destroy() and garantee that the framebufer object is unregistered - * from the drm_device idr pool. - */ -static void drm_test_framebuffer_free(struct kunit *test) -{ - struct drm_framebuffer_test_priv *priv = test->priv; - struct drm_device *dev = &priv->dev; - struct drm_mode_object *obj; - struct drm_framebuffer fb = { - .dev = dev, - .funcs = &framebuffer_funcs_free_mock, - }; - int id, ret; - - priv->buffer_freed = false; - - /* - * Mock a framebuffer that was not unregistered at the moment of the - * drm_framebuffer_free() call. - */ - ret = drm_mode_object_add(dev, &fb.base, DRM_MODE_OBJECT_FB); - KUNIT_ASSERT_EQ(test, ret, 0); - id = fb.base.id; - - drm_framebuffer_free(&fb.base.refcount); - - /* The framebuffer object must be unregistered */ - obj = drm_mode_object_find(dev, NULL, id, DRM_MODE_OBJECT_FB); - KUNIT_EXPECT_PTR_EQ(test, obj, NULL); - KUNIT_EXPECT_EQ(test, fb.base.id, 0); - - /* Test if fb->funcs->destroy() was called */ - KUNIT_EXPECT_EQ(test, priv->buffer_freed, true); -} - static struct kunit_case drm_framebuffer_tests[] = { KUNIT_CASE_PARAM(drm_test_framebuffer_check_src_coords, check_src_coords_gen_params), KUNIT_CASE(drm_test_framebuffer_cleanup), KUNIT_CASE_PARAM(drm_test_framebuffer_create, drm_framebuffer_create_gen_params), - KUNIT_CASE(drm_test_framebuffer_free), KUNIT_CASE(drm_test_framebuffer_init), KUNIT_CASE(drm_test_framebuffer_init_bad_format), KUNIT_CASE(drm_test_framebuffer_init_dev_mismatch), -- 2.39.2 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* [PATCH 2/2] Revert "drm/tests: Add test for drm_framebuffer_init()" 2024-09-17 17:43 [PATCH 0/2] drm: revert some framebuffer API tests Jani Nikula 2024-09-17 17:43 ` [PATCH 1/2] Revert "drm/tests: Add test for drm_framebuffer_free()" Jani Nikula @ 2024-09-17 17:43 ` Jani Nikula 2024-09-17 19:01 ` ✗ Fi.CI.SPARSE: warning for drm: revert some framebuffer API tests Patchwork ` (3 subsequent siblings) 5 siblings, 0 replies; 24+ messages in thread From: Jani Nikula @ 2024-09-17 17:43 UTC (permalink / raw) To: dri-devel Cc: intel-gfx, jani.nikula, Carlos Eduardo Gallo Filho, Maxime Ripard, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson This reverts commit 2735d5e4060960c7bd06698b0a1990c7d42c762e. This test hits a WARN_ON_ONCE(), because fb.format isn't set. Fixes: 2735d5e40609 ("drm/tests: Add test for drm_framebuffer_init()") Cc: Carlos Eduardo Gallo Filho <gcarlos@disroot.org> Cc: Maxime Ripard <mripard@kernel.org> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Cc: Thomas Zimmermann <tzimmermann@suse.de> Cc: Jeff Johnson <quic_jjohnson@quicinc.com> Signed-off-by: Jani Nikula <jani.nikula@intel.com> --- drivers/gpu/drm/drm_framebuffer.c | 1 - drivers/gpu/drm/tests/drm_framebuffer_test.c | 84 -------------------- 2 files changed, 85 deletions(-) diff --git a/drivers/gpu/drm/drm_framebuffer.c b/drivers/gpu/drm/drm_framebuffer.c index 47e6e8577b62..9cd85ac789bb 100644 --- a/drivers/gpu/drm/drm_framebuffer.c +++ b/drivers/gpu/drm/drm_framebuffer.c @@ -839,7 +839,6 @@ void drm_framebuffer_free(struct kref *kref) fb->funcs->destroy(fb); } -EXPORT_SYMBOL_FOR_TESTS_ONLY(drm_framebuffer_free); /** * drm_framebuffer_init - initialize a framebuffer diff --git a/drivers/gpu/drm/tests/drm_framebuffer_test.c b/drivers/gpu/drm/tests/drm_framebuffer_test.c index 72314805839d..e11b5bc9a105 100644 --- a/drivers/gpu/drm/tests/drm_framebuffer_test.c +++ b/drivers/gpu/drm/tests/drm_framebuffer_test.c @@ -5,7 +5,6 @@ * Copyright (c) 2022 Maíra Canal <mairacanal@riseup.net> */ -#include <kunit/device.h> #include <kunit/test.h> #include <drm/drm_device.h> @@ -569,93 +568,10 @@ static void drm_test_framebuffer_lookup_inexistent(struct kunit *test) KUNIT_EXPECT_NULL(test, fb); } -/* - * Test if drm_framebuffer_init initializes the framebuffer successfully, - * asserting that its modeset object struct and its refcount are correctly - * set and that strictly one framebuffer is initialized. - */ -static void drm_test_framebuffer_init(struct kunit *test) -{ - struct drm_framebuffer_test_priv *priv = test->priv; - struct drm_device *dev = &priv->dev; - struct drm_format_info format = { }; - struct drm_framebuffer fb1 = { .dev = dev, .format = &format }; - struct drm_framebuffer_funcs funcs = { }; - int ret; - - ret = drm_framebuffer_init(dev, &fb1, &funcs); - KUNIT_ASSERT_EQ(test, ret, 0); - - /* Check if fb->funcs is actually set to the drm_framebuffer_funcs passed on */ - KUNIT_EXPECT_PTR_EQ(test, fb1.funcs, &funcs); - - /* The fb->comm must be set to the current running process */ - KUNIT_EXPECT_STREQ(test, fb1.comm, current->comm); - - /* The fb->base must be successfully initialized */ - KUNIT_EXPECT_NE(test, fb1.base.id, 0); - KUNIT_EXPECT_EQ(test, fb1.base.type, DRM_MODE_OBJECT_FB); - KUNIT_EXPECT_EQ(test, kref_read(&fb1.base.refcount), 1); - KUNIT_EXPECT_PTR_EQ(test, fb1.base.free_cb, &drm_framebuffer_free); - - /* There must be just that one fb initialized */ - KUNIT_EXPECT_EQ(test, dev->mode_config.num_fb, 1); - KUNIT_EXPECT_PTR_EQ(test, dev->mode_config.fb_list.prev, &fb1.head); - KUNIT_EXPECT_PTR_EQ(test, dev->mode_config.fb_list.next, &fb1.head); - - drm_framebuffer_cleanup(&fb1); -} - -/* Try to init a framebuffer without setting its format */ -static void drm_test_framebuffer_init_bad_format(struct kunit *test) -{ - struct drm_framebuffer_test_priv *priv = test->priv; - struct drm_device *dev = &priv->dev; - struct drm_framebuffer fb1 = { .dev = dev, .format = NULL }; - struct drm_framebuffer_funcs funcs = { }; - int ret; - - /* Fails if fb.format isn't set */ - ret = drm_framebuffer_init(dev, &fb1, &funcs); - KUNIT_EXPECT_EQ(test, ret, -EINVAL); -} - -/* - * Test calling drm_framebuffer_init() passing a framebuffer linked to a - * different drm_device parent from the one passed on the first argument, which - * must fail. - */ -static void drm_test_framebuffer_init_dev_mismatch(struct kunit *test) -{ - struct drm_framebuffer_test_priv *priv = test->priv; - struct drm_device *right_dev = &priv->dev; - struct drm_device *wrong_dev; - struct device *wrong_dev_parent; - struct drm_format_info format = { }; - struct drm_framebuffer fb1 = { .dev = right_dev, .format = &format }; - struct drm_framebuffer_funcs funcs = { }; - int ret; - - wrong_dev_parent = kunit_device_register(test, "drm-kunit-wrong-device-mock"); - KUNIT_ASSERT_NOT_ERR_OR_NULL(test, wrong_dev_parent); - - wrong_dev = __drm_kunit_helper_alloc_drm_device(test, wrong_dev_parent, - sizeof(struct drm_device), - 0, 0); - KUNIT_ASSERT_NOT_ERR_OR_NULL(test, wrong_dev); - - /* Fails if fb->dev doesn't point to the drm_device passed on first arg */ - ret = drm_framebuffer_init(wrong_dev, &fb1, &funcs); - KUNIT_EXPECT_EQ(test, ret, -EINVAL); -} - static struct kunit_case drm_framebuffer_tests[] = { KUNIT_CASE_PARAM(drm_test_framebuffer_check_src_coords, check_src_coords_gen_params), KUNIT_CASE(drm_test_framebuffer_cleanup), KUNIT_CASE_PARAM(drm_test_framebuffer_create, drm_framebuffer_create_gen_params), - KUNIT_CASE(drm_test_framebuffer_init), - KUNIT_CASE(drm_test_framebuffer_init_bad_format), - KUNIT_CASE(drm_test_framebuffer_init_dev_mismatch), KUNIT_CASE(drm_test_framebuffer_lookup), KUNIT_CASE(drm_test_framebuffer_lookup_inexistent), KUNIT_CASE(drm_test_framebuffer_modifiers_not_supported), -- 2.39.2 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* ✗ Fi.CI.SPARSE: warning for drm: revert some framebuffer API tests 2024-09-17 17:43 [PATCH 0/2] drm: revert some framebuffer API tests Jani Nikula 2024-09-17 17:43 ` [PATCH 1/2] Revert "drm/tests: Add test for drm_framebuffer_free()" Jani Nikula 2024-09-17 17:43 ` [PATCH 2/2] Revert "drm/tests: Add test for drm_framebuffer_init()" Jani Nikula @ 2024-09-17 19:01 ` Patchwork 2024-09-17 19:10 ` ✓ Fi.CI.BAT: success " Patchwork ` (2 subsequent siblings) 5 siblings, 0 replies; 24+ messages in thread From: Patchwork @ 2024-09-17 19:01 UTC (permalink / raw) To: Jani Nikula; +Cc: intel-gfx == Series Details == Series: drm: revert some framebuffer API tests URL : https://patchwork.freedesktop.org/series/138782/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. +./arch/x86/include/asm/bitops.h:116:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:147:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:149:9: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:153:26: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:155:16: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:155:9: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:173:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:175:9: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:179:35: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:181:16: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:181:9: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:185:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:187:9: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:191:35: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:194:16: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:194:9: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:236:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:238:9: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:243:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:245:9: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:66:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:92:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:100:17: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:100:23: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:100:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:105:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:107:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:108:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:109:9: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:111:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:111:14: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:111:20: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:112:17: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:112:23: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:112:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:121:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:128:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:137:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:139:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:140:23: warning: unreplaced symbol 'break' +./include/asm-generic/bitops/generic-non-atomic.h:140:23: warning: unreplaced symbol 'continue' +./include/asm-generic/bitops/generic-non-atomic.h:140:23: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:140:23: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:140:23: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:140:23: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:140:23: warning: unreplaced symbol '___p1' +./include/asm-generic/bitops/generic-non-atomic.h:140:23: warning: unreplaced symbol '___p1' +./include/asm-generic/bitops/generic-non-atomic.h:140:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:166:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:168:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:169:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:170:9: warning: unreplaced symbol 'val' +./include/asm-generic/bitops/generic-non-atomic.h:172:19: warning: unreplaced symbol 'val' +./include/asm-generic/bitops/generic-non-atomic.h:172:25: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:172:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:28:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:30:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:31:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:33:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:33:16: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:37:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:39:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:40:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:42:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:42:16: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:55:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:57:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:58:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:60:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:60:15: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:73:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:75:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:76:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:77:9: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:79:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:79:14: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:79:20: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:80:17: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:80:23: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:80:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:93:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:95:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:96:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:97:9: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:99:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:99:14: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:99:21: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/instrumented-non-atomic.h:100:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:112:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:115:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:127:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:130:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:139:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:142:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:151:1: warning: too many warnings +./include/asm-generic/bitops/instrumented-non-atomic.h:154:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:26:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:42:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:58:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:97:1: warning: unreplaced symbol 'return' ^ permalink raw reply [flat|nested] 24+ messages in thread
* ✓ Fi.CI.BAT: success for drm: revert some framebuffer API tests 2024-09-17 17:43 [PATCH 0/2] drm: revert some framebuffer API tests Jani Nikula ` (2 preceding siblings ...) 2024-09-17 19:01 ` ✗ Fi.CI.SPARSE: warning for drm: revert some framebuffer API tests Patchwork @ 2024-09-17 19:10 ` Patchwork 2024-09-18 8:44 ` ✗ Fi.CI.IGT: failure " Patchwork 2024-09-24 10:06 ` [PATCH 0/2] " Simona Vetter 5 siblings, 0 replies; 24+ messages in thread From: Patchwork @ 2024-09-17 19:10 UTC (permalink / raw) To: Jani Nikula; +Cc: intel-gfx [-- Attachment #1: Type: text/plain, Size: 9299 bytes --] == Series Details == Series: drm: revert some framebuffer API tests URL : https://patchwork.freedesktop.org/series/138782/ State : success == Summary == CI Bug Log - changes from CI_DRM_15429 -> Patchwork_138782v1 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/index.html Participating hosts (40 -> 36) ------------------------------ Additional (1): bat-mtlp-6 Missing (5): bat-arlh-3 fi-bsw-n3050 fi-ilk-650 fi-snb-2520m fi-kbl-8809g Known issues ------------ Here are the changes found in Patchwork_138782v1 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@debugfs_test@basic-hwmon: - bat-mtlp-6: NOTRUN -> [SKIP][1] ([i915#9318]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@debugfs_test@basic-hwmon.html * igt@fbdev@info: - bat-mtlp-6: NOTRUN -> [SKIP][2] ([i915#1849] / [i915#2582]) [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@fbdev@info.html * igt@fbdev@write: - bat-mtlp-6: NOTRUN -> [SKIP][3] ([i915#2582]) +3 other tests skip [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@fbdev@write.html * igt@gem_lmem_swapping@verify-random: - bat-mtlp-6: NOTRUN -> [SKIP][4] ([i915#4613]) +3 other tests skip [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@gem_lmem_swapping@verify-random.html * igt@gem_mmap@basic: - bat-mtlp-6: NOTRUN -> [SKIP][5] ([i915#4083]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@gem_mmap@basic.html * igt@gem_tiled_blits@basic: - bat-mtlp-6: NOTRUN -> [SKIP][6] ([i915#4077]) +2 other tests skip [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@gem_tiled_blits@basic.html * igt@gem_tiled_pread_basic: - bat-mtlp-6: NOTRUN -> [SKIP][7] ([i915#4079]) +1 other test skip [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@gem_tiled_pread_basic.html * igt@i915_module_load@load: - bat-adlp-6: [PASS][8] -> [DMESG-WARN][9] ([i915#12037]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/bat-adlp-6/igt@i915_module_load@load.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-adlp-6/igt@i915_module_load@load.html * igt@i915_pm_rps@basic-api: - bat-mtlp-6: NOTRUN -> [SKIP][10] ([i915#11681] / [i915#6621]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@i915_pm_rps@basic-api.html * igt@i915_selftest@live: - bat-arls-2: [PASS][11] -> [DMESG-WARN][12] ([i915#10341] / [i915#12133]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/bat-arls-2/igt@i915_selftest@live.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-arls-2/igt@i915_selftest@live.html * igt@i915_selftest@live@hangcheck: - bat-arls-2: [PASS][13] -> [DMESG-WARN][14] ([i915#11349]) [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/bat-arls-2/igt@i915_selftest@live@hangcheck.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-arls-2/igt@i915_selftest@live@hangcheck.html * igt@kms_addfb_basic@addfb25-x-tiled-legacy: - bat-mtlp-6: NOTRUN -> [SKIP][15] ([i915#4212] / [i915#9792]) +8 other tests skip [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@kms_addfb_basic@addfb25-x-tiled-legacy.html * igt@kms_addfb_basic@addfb25-y-tiled-small-legacy: - bat-mtlp-6: NOTRUN -> [SKIP][16] ([i915#5190] / [i915#9792]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@kms_addfb_basic@addfb25-y-tiled-small-legacy.html * igt@kms_cursor_legacy@basic-flip-after-cursor-legacy: - bat-mtlp-6: NOTRUN -> [SKIP][17] ([i915#9792]) +17 other tests skip [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@kms_cursor_legacy@basic-flip-after-cursor-legacy.html * igt@kms_flip@basic-flip-vs-dpms: - bat-mtlp-6: NOTRUN -> [SKIP][18] ([i915#3637] / [i915#9792]) +3 other tests skip [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@kms_flip@basic-flip-vs-dpms.html * igt@kms_force_connector_basic@prune-stale-modes: - bat-mtlp-6: NOTRUN -> [SKIP][19] ([i915#5274] / [i915#9792]) [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@kms_force_connector_basic@prune-stale-modes.html * igt@kms_frontbuffer_tracking@basic: - bat-mtlp-6: NOTRUN -> [SKIP][20] ([i915#4342] / [i915#5354] / [i915#9792]) [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@kms_frontbuffer_tracking@basic.html * igt@kms_pm_backlight@basic-brightness: - bat-mtlp-6: NOTRUN -> [SKIP][21] ([i915#5354] / [i915#9792]) [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@kms_pm_backlight@basic-brightness.html * igt@kms_psr@psr-cursor-plane-move: - bat-mtlp-6: NOTRUN -> [SKIP][22] ([i915#1072] / [i915#9673] / [i915#9732] / [i915#9792]) +3 other tests skip [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@kms_psr@psr-cursor-plane-move.html * igt@kms_setmode@basic-clone-single-crtc: - bat-mtlp-6: NOTRUN -> [SKIP][23] ([i915#3555] / [i915#8809] / [i915#9792]) [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@kms_setmode@basic-clone-single-crtc.html * igt@prime_vgem@basic-fence-flip: - bat-mtlp-6: NOTRUN -> [SKIP][24] ([i915#3708] / [i915#9792]) [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@prime_vgem@basic-fence-flip.html * igt@prime_vgem@basic-fence-mmap: - bat-mtlp-6: NOTRUN -> [SKIP][25] ([i915#3708] / [i915#4077]) +1 other test skip [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@prime_vgem@basic-fence-mmap.html * igt@prime_vgem@basic-read: - bat-mtlp-6: NOTRUN -> [SKIP][26] ([i915#3708]) +1 other test skip [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@prime_vgem@basic-read.html * igt@prime_vgem@basic-write: - bat-mtlp-6: NOTRUN -> [SKIP][27] ([i915#10216] / [i915#3708]) [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/bat-mtlp-6/igt@prime_vgem@basic-write.html [i915#10216]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10216 [i915#10341]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10341 [i915#1072]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1072 [i915#11349]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11349 [i915#11681]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11681 [i915#12037]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12037 [i915#12133]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12133 [i915#1849]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1849 [i915#2582]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2582 [i915#3555]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3555 [i915#3637]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3637 [i915#3708]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3708 [i915#4077]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4077 [i915#4079]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4079 [i915#4083]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4083 [i915#4212]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4212 [i915#4342]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4342 [i915#4613]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4613 [i915#5190]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5190 [i915#5274]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5274 [i915#5354]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5354 [i915#6621]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6621 [i915#8809]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8809 [i915#9318]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9318 [i915#9673]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9673 [i915#9732]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9732 [i915#9792]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9792 Build changes ------------- * Linux: CI_DRM_15429 -> Patchwork_138782v1 CI-20190529: 20190529 CI_DRM_15429: 38e1b615fb395b928e514108e908cd6edf3d34c3 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_8022: 2d82f767a959d58c04ff3876d59d67924208d4ef @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_138782v1: 38e1b615fb395b928e514108e908cd6edf3d34c3 @ git://anongit.freedesktop.org/gfx-ci/linux == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/index.html [-- Attachment #2: Type: text/html, Size: 11590 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
* ✗ Fi.CI.IGT: failure for drm: revert some framebuffer API tests 2024-09-17 17:43 [PATCH 0/2] drm: revert some framebuffer API tests Jani Nikula ` (3 preceding siblings ...) 2024-09-17 19:10 ` ✓ Fi.CI.BAT: success " Patchwork @ 2024-09-18 8:44 ` Patchwork 2024-09-24 10:06 ` [PATCH 0/2] " Simona Vetter 5 siblings, 0 replies; 24+ messages in thread From: Patchwork @ 2024-09-18 8:44 UTC (permalink / raw) To: Jani Nikula; +Cc: intel-gfx [-- Attachment #1: Type: text/plain, Size: 82112 bytes --] == Series Details == Series: drm: revert some framebuffer API tests URL : https://patchwork.freedesktop.org/series/138782/ State : failure == Summary == CI Bug Log - changes from CI_DRM_15429_full -> Patchwork_138782v1_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_138782v1_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_138782v1_full, 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 Patchwork_138782v1_full: ### IGT changes ### #### Possible regressions #### * igt@kms_flip@absolute-wf_vblank@b-hdmi-a2: - shard-glk: [PASS][1] -> [INCOMPLETE][2] +1 other test incomplete [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-glk2/igt@kms_flip@absolute-wf_vblank@b-hdmi-a2.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-glk2/igt@kms_flip@absolute-wf_vblank@b-hdmi-a2.html New tests --------- New tests have been introduced between CI_DRM_15429_full and Patchwork_138782v1_full: ### New IGT tests (3) ### * igt@kms_selftest@drm_framebuffer@drm_test_framebuffer_lookup: - Statuses : 7 pass(s) - Exec time: [0.06, 0.13] s * igt@kms_selftest@drm_framebuffer@drm_test_framebuffer_lookup_inexistent: - Statuses : 7 pass(s) - Exec time: [0.06, 0.12] s * igt@kms_selftest@drm_framebuffer@drm_test_framebuffer_modifiers_not_supported: - Statuses : 7 pass(s) - Exec time: [0.06, 0.11] s Known issues ------------ Here are the changes found in Patchwork_138782v1_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@api_intel_bb@blit-reloc-purge-cache: - shard-dg1: NOTRUN -> [SKIP][3] ([i915#8411]) +1 other test skip [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@api_intel_bb@blit-reloc-purge-cache.html * igt@api_intel_bb@object-reloc-purge-cache: - shard-mtlp: NOTRUN -> [SKIP][4] ([i915#8411]) [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-7/igt@api_intel_bb@object-reloc-purge-cache.html - shard-dg2: NOTRUN -> [SKIP][5] ([i915#8411]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-3/igt@api_intel_bb@object-reloc-purge-cache.html - shard-rkl: NOTRUN -> [SKIP][6] ([i915#8411]) [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-5/igt@api_intel_bb@object-reloc-purge-cache.html * igt@device_reset@unbind-reset-rebind: - shard-dg1: NOTRUN -> [ABORT][7] ([i915#11814] / [i915#11815]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-17/igt@device_reset@unbind-reset-rebind.html * igt@drm_fdinfo@busy-idle@bcs0: - shard-mtlp: NOTRUN -> [SKIP][8] ([i915#8414]) +6 other tests skip [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@drm_fdinfo@busy-idle@bcs0.html * igt@drm_fdinfo@isolation: - shard-dg1: NOTRUN -> [SKIP][9] ([i915#8414]) +6 other tests skip [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@drm_fdinfo@isolation.html * igt@drm_fdinfo@most-busy-idle-check-all@vecs1: - shard-dg2: NOTRUN -> [SKIP][10] ([i915#8414]) +7 other tests skip [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@drm_fdinfo@most-busy-idle-check-all@vecs1.html * igt@gem_caching@writes: - shard-mtlp: NOTRUN -> [SKIP][11] ([i915#4873]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@gem_caching@writes.html * igt@gem_ccs@block-multicopy-inplace: - shard-rkl: NOTRUN -> [SKIP][12] ([i915#3555] / [i915#9323]) [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@gem_ccs@block-multicopy-inplace.html * igt@gem_ccs@ctrl-surf-copy-new-ctx: - shard-mtlp: NOTRUN -> [SKIP][13] ([i915#9323]) [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@gem_ccs@ctrl-surf-copy-new-ctx.html * igt@gem_ccs@suspend-resume: - shard-dg2: [PASS][14] -> [INCOMPLETE][15] ([i915#7297]) +1 other test incomplete [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-11/igt@gem_ccs@suspend-resume.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-4/igt@gem_ccs@suspend-resume.html * igt@gem_ctx_engines@invalid-engines: - shard-glk: [PASS][16] -> [FAIL][17] ([i915#12027]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-glk9/igt@gem_ctx_engines@invalid-engines.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-glk6/igt@gem_ctx_engines@invalid-engines.html - shard-rkl: [PASS][18] -> [FAIL][19] ([i915#12027]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-rkl-5/igt@gem_ctx_engines@invalid-engines.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-5/igt@gem_ctx_engines@invalid-engines.html * igt@gem_ctx_persistence@heartbeat-many: - shard-dg1: NOTRUN -> [SKIP][20] ([i915#8555]) [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@gem_ctx_persistence@heartbeat-many.html * igt@gem_ctx_sseu@invalid-args: - shard-dg1: NOTRUN -> [SKIP][21] ([i915#280]) +1 other test skip [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@gem_ctx_sseu@invalid-args.html * igt@gem_ctx_sseu@mmap-args: - shard-mtlp: NOTRUN -> [SKIP][22] ([i915#280]) [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@gem_ctx_sseu@mmap-args.html * igt@gem_exec_balancer@bonded-dual: - shard-dg1: NOTRUN -> [SKIP][23] ([i915#4771]) [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@gem_exec_balancer@bonded-dual.html * igt@gem_exec_balancer@sliced: - shard-dg1: NOTRUN -> [SKIP][24] ([i915#4812]) +1 other test skip [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@gem_exec_balancer@sliced.html * igt@gem_exec_fair@basic-none-solo: - shard-glk: NOTRUN -> [FAIL][25] ([i915#2842]) +1 other test fail [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-glk5/igt@gem_exec_fair@basic-none-solo.html * igt@gem_exec_fair@basic-pace-solo: - shard-dg2: NOTRUN -> [SKIP][26] ([i915#3539]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@gem_exec_fair@basic-pace-solo.html * igt@gem_exec_fair@basic-pace@bcs0: - shard-rkl: [PASS][27] -> [FAIL][28] ([i915#2842]) [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-rkl-6/igt@gem_exec_fair@basic-pace@bcs0.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-2/igt@gem_exec_fair@basic-pace@bcs0.html * igt@gem_exec_fair@basic-throttle: - shard-rkl: NOTRUN -> [FAIL][29] ([i915#2842]) +3 other tests fail [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@gem_exec_fair@basic-throttle.html * igt@gem_exec_fence@concurrent: - shard-mtlp: NOTRUN -> [SKIP][30] ([i915#4812]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@gem_exec_fence@concurrent.html * igt@gem_exec_flush@basic-batch-kernel-default-cmd: - shard-dg1: NOTRUN -> [SKIP][31] ([i915#3539] / [i915#4852]) +1 other test skip [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@gem_exec_flush@basic-batch-kernel-default-cmd.html * igt@gem_exec_reloc@basic-gtt-cpu-active: - shard-dg2: NOTRUN -> [SKIP][32] ([i915#3281]) +1 other test skip [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@gem_exec_reloc@basic-gtt-cpu-active.html * igt@gem_exec_reloc@basic-wc-cpu: - shard-dg1: NOTRUN -> [SKIP][33] ([i915#3281]) +7 other tests skip [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@gem_exec_reloc@basic-wc-cpu.html * igt@gem_exec_reloc@basic-wc-read-active: - shard-mtlp: NOTRUN -> [SKIP][34] ([i915#3281]) +4 other tests skip [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@gem_exec_reloc@basic-wc-read-active.html * igt@gem_exec_reloc@basic-write-read-noreloc: - shard-rkl: NOTRUN -> [SKIP][35] ([i915#3281]) +3 other tests skip [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@gem_exec_reloc@basic-write-read-noreloc.html * igt@gem_exec_schedule@semaphore-power: - shard-rkl: NOTRUN -> [SKIP][36] ([i915#7276]) [36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@gem_exec_schedule@semaphore-power.html * igt@gem_lmem_swapping@parallel-multi: - shard-rkl: NOTRUN -> [SKIP][37] ([i915#4613]) +2 other tests skip [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@gem_lmem_swapping@parallel-multi.html * igt@gem_lmem_swapping@parallel-random-verify-ccs: - shard-glk: NOTRUN -> [SKIP][38] ([i915#4613]) [38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-glk8/igt@gem_lmem_swapping@parallel-random-verify-ccs.html * igt@gem_lmem_swapping@verify-random: - shard-tglu: NOTRUN -> [SKIP][39] ([i915#4613]) [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@gem_lmem_swapping@verify-random.html * igt@gem_mmap_gtt@cpuset-medium-copy: - shard-mtlp: NOTRUN -> [SKIP][40] ([i915#4077]) +8 other tests skip [40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-7/igt@gem_mmap_gtt@cpuset-medium-copy.html * igt@gem_mmap_wc@bad-object: - shard-dg2: NOTRUN -> [SKIP][41] ([i915#4083]) +1 other test skip [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@gem_mmap_wc@bad-object.html * igt@gem_mmap_wc@write-read-distinct: - shard-dg1: NOTRUN -> [SKIP][42] ([i915#4083]) +2 other tests skip [42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@gem_mmap_wc@write-read-distinct.html * igt@gem_partial_pwrite_pread@reads-snoop: - shard-mtlp: NOTRUN -> [SKIP][43] ([i915#3282]) +2 other tests skip [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@gem_partial_pwrite_pread@reads-snoop.html * igt@gem_partial_pwrite_pread@reads-uncached: - shard-dg2: NOTRUN -> [SKIP][44] ([i915#3282]) +2 other tests skip [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@gem_partial_pwrite_pread@reads-uncached.html * igt@gem_partial_pwrite_pread@write-display: - shard-dg1: NOTRUN -> [SKIP][45] ([i915#3282]) +2 other tests skip [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@gem_partial_pwrite_pread@write-display.html * igt@gem_partial_pwrite_pread@writes-after-reads-uncached: - shard-rkl: NOTRUN -> [SKIP][46] ([i915#3282]) +5 other tests skip [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@gem_partial_pwrite_pread@writes-after-reads-uncached.html * igt@gem_pxp@create-valid-protected-context: - shard-dg2: NOTRUN -> [SKIP][47] ([i915#4270]) [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@gem_pxp@create-valid-protected-context.html * igt@gem_pxp@display-protected-crc: - shard-rkl: NOTRUN -> [SKIP][48] ([i915#4270]) +1 other test skip [48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@gem_pxp@display-protected-crc.html * igt@gem_pxp@reject-modify-context-protection-off-1: - shard-tglu: NOTRUN -> [SKIP][49] ([i915#4270]) [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@gem_pxp@reject-modify-context-protection-off-1.html * igt@gem_pxp@verify-pxp-key-change-after-suspend-resume: - shard-dg1: NOTRUN -> [SKIP][50] ([i915#4270]) +3 other tests skip [50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@gem_pxp@verify-pxp-key-change-after-suspend-resume.html * igt@gem_render_copy@y-tiled-ccs-to-y-tiled-mc-ccs: - shard-mtlp: NOTRUN -> [SKIP][51] ([i915#8428]) [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@gem_render_copy@y-tiled-ccs-to-y-tiled-mc-ccs.html * igt@gem_render_copy@y-tiled-mc-ccs-to-yf-tiled-ccs: - shard-dg2: NOTRUN -> [SKIP][52] ([i915#5190] / [i915#8428]) [52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@gem_render_copy@y-tiled-mc-ccs-to-yf-tiled-ccs.html * igt@gem_tiled_swapping@non-threaded: - shard-dg2: NOTRUN -> [SKIP][53] ([i915#4077]) +4 other tests skip [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@gem_tiled_swapping@non-threaded.html * igt@gem_userptr_blits@access-control: - shard-dg2: NOTRUN -> [SKIP][54] ([i915#3297]) [54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@gem_userptr_blits@access-control.html * igt@gem_userptr_blits@forbidden-operations: - shard-dg1: NOTRUN -> [SKIP][55] ([i915#3282] / [i915#3297]) [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@gem_userptr_blits@forbidden-operations.html * igt@gem_userptr_blits@map-fixed-invalidate: - shard-dg1: NOTRUN -> [SKIP][56] ([i915#3297] / [i915#4880]) [56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@gem_userptr_blits@map-fixed-invalidate.html * igt@gem_userptr_blits@readonly-pwrite-unsync: - shard-dg1: NOTRUN -> [SKIP][57] ([i915#3297]) [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@gem_userptr_blits@readonly-pwrite-unsync.html * igt@gen9_exec_parse@basic-rejected-ctx-param: - shard-dg1: NOTRUN -> [SKIP][58] ([i915#2527]) [58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@gen9_exec_parse@basic-rejected-ctx-param.html * igt@gen9_exec_parse@bb-oversize: - shard-mtlp: NOTRUN -> [SKIP][59] ([i915#2856]) [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@gen9_exec_parse@bb-oversize.html * igt@gen9_exec_parse@bb-start-far: - shard-rkl: NOTRUN -> [SKIP][60] ([i915#2527]) [60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@gen9_exec_parse@bb-start-far.html * igt@gen9_exec_parse@shadow-peek: - shard-tglu: NOTRUN -> [SKIP][61] ([i915#2527] / [i915#2856]) +1 other test skip [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@gen9_exec_parse@shadow-peek.html * igt@i915_fb_tiling: - shard-dg1: NOTRUN -> [SKIP][62] ([i915#4881]) [62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@i915_fb_tiling.html * igt@i915_module_load@reload-with-fault-injection: - shard-dg1: [PASS][63] -> [ABORT][64] ([i915#9820]) [63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg1-16/igt@i915_module_load@reload-with-fault-injection.html [64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-14/igt@i915_module_load@reload-with-fault-injection.html * igt@i915_module_load@resize-bar: - shard-mtlp: NOTRUN -> [SKIP][65] ([i915#6412]) [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@i915_module_load@resize-bar.html * igt@i915_pm_freq_api@freq-reset-multiple: - shard-rkl: NOTRUN -> [SKIP][66] ([i915#8399]) [66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@i915_pm_freq_api@freq-reset-multiple.html * igt@i915_pm_rps@min-max-config-idle: - shard-dg1: NOTRUN -> [SKIP][67] ([i915#11681] / [i915#6621]) [67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@i915_pm_rps@min-max-config-idle.html * igt@i915_selftest@mock@memory_region: - shard-dg1: NOTRUN -> [DMESG-WARN][68] ([i915#9311]) +1 other test dmesg-warn [68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@i915_selftest@mock@memory_region.html * igt@i915_suspend@basic-s3-without-i915: - shard-mtlp: NOTRUN -> [SKIP][69] ([i915#6645]) [69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@i915_suspend@basic-s3-without-i915.html * igt@i915_suspend@fence-restore-untiled: - shard-dg1: NOTRUN -> [SKIP][70] ([i915#4077]) +6 other tests skip [70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@i915_suspend@fence-restore-untiled.html * igt@intel_hwmon@hwmon-read: - shard-rkl: NOTRUN -> [SKIP][71] ([i915#7707]) [71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@intel_hwmon@hwmon-read.html * igt@kms_async_flips@async-flip-with-page-flip-events@pipe-b-hdmi-a-4-y-rc-ccs: - shard-dg1: NOTRUN -> [SKIP][72] ([i915#8709]) +7 other tests skip [72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_async_flips@async-flip-with-page-flip-events@pipe-b-hdmi-a-4-y-rc-ccs.html * igt@kms_atomic_transition@modeset-transition-fencing: - shard-glk: [PASS][73] -> [FAIL][74] ([i915#12238]) [73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-glk3/igt@kms_atomic_transition@modeset-transition-fencing.html [74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-glk8/igt@kms_atomic_transition@modeset-transition-fencing.html * igt@kms_atomic_transition@modeset-transition-fencing@2x-outputs: - shard-glk: [PASS][75] -> [FAIL][76] ([i915#11859]) [75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-glk3/igt@kms_atomic_transition@modeset-transition-fencing@2x-outputs.html [76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-glk8/igt@kms_atomic_transition@modeset-transition-fencing@2x-outputs.html * igt@kms_atomic_transition@plane-all-modeset-transition-fencing-internal-panels: - shard-glk: NOTRUN -> [SKIP][77] ([i915#1769]) [77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-glk5/igt@kms_atomic_transition@plane-all-modeset-transition-fencing-internal-panels.html * igt@kms_atomic_transition@plane-all-modeset-transition-internal-panels: - shard-dg1: NOTRUN -> [SKIP][78] ([i915#1769] / [i915#3555]) [78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_atomic_transition@plane-all-modeset-transition-internal-panels.html * igt@kms_atomic_transition@plane-toggle-modeset-transition@pipe-a-hdmi-a-1: - shard-snb: [PASS][79] -> [FAIL][80] ([i915#5956]) +1 other test fail [79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-snb5/igt@kms_atomic_transition@plane-toggle-modeset-transition@pipe-a-hdmi-a-1.html [80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-snb6/igt@kms_atomic_transition@plane-toggle-modeset-transition@pipe-a-hdmi-a-1.html - shard-tglu: [PASS][81] -> [FAIL][82] ([i915#11808]) +1 other test fail [81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-tglu-8/igt@kms_atomic_transition@plane-toggle-modeset-transition@pipe-a-hdmi-a-1.html [82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-10/igt@kms_atomic_transition@plane-toggle-modeset-transition@pipe-a-hdmi-a-1.html * igt@kms_big_fb@4-tiled-addfb: - shard-rkl: NOTRUN -> [SKIP][83] ([i915#5286]) +3 other tests skip [83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_big_fb@4-tiled-addfb.html * igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-180-async-flip: - shard-dg1: NOTRUN -> [SKIP][84] ([i915#4538] / [i915#5286]) +3 other tests skip [84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html * igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-180: - shard-tglu: NOTRUN -> [SKIP][85] ([i915#5286]) +1 other test skip [85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-7/igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-180.html * igt@kms_big_fb@linear-64bpp-rotate-90: - shard-rkl: NOTRUN -> [SKIP][86] ([i915#3638]) +1 other test skip [86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_big_fb@linear-64bpp-rotate-90.html * igt@kms_big_fb@y-tiled-64bpp-rotate-90: - shard-dg1: NOTRUN -> [SKIP][87] ([i915#3638]) +1 other test skip [87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_big_fb@y-tiled-64bpp-rotate-90.html * igt@kms_big_fb@yf-tiled-64bpp-rotate-180: - shard-dg2: NOTRUN -> [SKIP][88] ([i915#4538] / [i915#5190]) +2 other tests skip [88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_big_fb@yf-tiled-64bpp-rotate-180.html * igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-180: - shard-dg1: NOTRUN -> [SKIP][89] ([i915#4538]) +4 other tests skip [89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-180.html * igt@kms_big_joiner@basic-force-joiner: - shard-dg2: NOTRUN -> [SKIP][90] ([i915#10656]) [90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_big_joiner@basic-force-joiner.html * igt@kms_ccs@bad-aux-stride-yf-tiled-ccs@pipe-d-hdmi-a-2: - shard-dg2: NOTRUN -> [SKIP][91] ([i915#10307] / [i915#6095]) +169 other tests skip [91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-3/igt@kms_ccs@bad-aux-stride-yf-tiled-ccs@pipe-d-hdmi-a-2.html * igt@kms_ccs@bad-pixel-format-4-tiled-dg2-rc-ccs: - shard-mtlp: NOTRUN -> [SKIP][92] ([i915#6095]) +19 other tests skip [92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_ccs@bad-pixel-format-4-tiled-dg2-rc-ccs.html * igt@kms_ccs@bad-rotation-90-4-tiled-bmg-ccs: - shard-rkl: NOTRUN -> [SKIP][93] ([i915#12042]) [93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_ccs@bad-rotation-90-4-tiled-bmg-ccs.html * igt@kms_ccs@bad-rotation-90-4-tiled-mtl-rc-ccs-cc@pipe-b-hdmi-a-4: - shard-dg1: NOTRUN -> [SKIP][94] ([i915#6095]) +84 other tests skip [94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_ccs@bad-rotation-90-4-tiled-mtl-rc-ccs-cc@pipe-b-hdmi-a-4.html * igt@kms_ccs@ccs-on-another-bo-4-tiled-mtl-rc-ccs: - shard-tglu: NOTRUN -> [SKIP][95] ([i915#6095]) +19 other tests skip [95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-7/igt@kms_ccs@ccs-on-another-bo-4-tiled-mtl-rc-ccs.html * igt@kms_ccs@crc-primary-basic-4-tiled-mtl-mc-ccs@pipe-b-hdmi-a-1: - shard-rkl: NOTRUN -> [SKIP][96] ([i915#6095]) +48 other tests skip [96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_ccs@crc-primary-basic-4-tiled-mtl-mc-ccs@pipe-b-hdmi-a-1.html * igt@kms_ccs@crc-sprite-planes-basic-4-tiled-bmg-ccs: - shard-tglu: NOTRUN -> [SKIP][97] ([i915#12042]) [97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_ccs@crc-sprite-planes-basic-4-tiled-bmg-ccs.html * igt@kms_ccs@random-ccs-data-4-tiled-bmg-ccs: - shard-mtlp: NOTRUN -> [SKIP][98] ([i915#12042]) [98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_ccs@random-ccs-data-4-tiled-bmg-ccs.html * igt@kms_ccs@random-ccs-data-4-tiled-lnl-ccs: - shard-dg1: NOTRUN -> [SKIP][99] ([i915#12042]) +1 other test skip [99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_ccs@random-ccs-data-4-tiled-lnl-ccs.html * igt@kms_ccs@random-ccs-data-yf-tiled-ccs@pipe-d-hdmi-a-1: - shard-dg2: NOTRUN -> [SKIP][100] ([i915#10307] / [i915#10434] / [i915#6095]) +5 other tests skip [100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_ccs@random-ccs-data-yf-tiled-ccs@pipe-d-hdmi-a-1.html * igt@kms_cdclk@mode-transition: - shard-dg1: NOTRUN -> [SKIP][101] ([i915#3742]) [101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-17/igt@kms_cdclk@mode-transition.html * igt@kms_cdclk@mode-transition@pipe-d-hdmi-a-3: - shard-dg2: NOTRUN -> [SKIP][102] ([i915#7213]) +3 other tests skip [102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-7/igt@kms_cdclk@mode-transition@pipe-d-hdmi-a-3.html * igt@kms_chamelium_audio@hdmi-audio-edid: - shard-mtlp: NOTRUN -> [SKIP][103] ([i915#7828]) +3 other tests skip [103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@kms_chamelium_audio@hdmi-audio-edid.html * igt@kms_chamelium_frames@dp-crc-fast: - shard-tglu: NOTRUN -> [SKIP][104] ([i915#7828]) +1 other test skip [104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_chamelium_frames@dp-crc-fast.html * igt@kms_chamelium_frames@dp-frame-dump: - shard-dg2: NOTRUN -> [SKIP][105] ([i915#7828]) +1 other test skip [105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_chamelium_frames@dp-frame-dump.html * igt@kms_chamelium_hpd@dp-hpd-fast: - shard-dg1: NOTRUN -> [SKIP][106] ([i915#7828]) +3 other tests skip [106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_chamelium_hpd@dp-hpd-fast.html * igt@kms_chamelium_hpd@hdmi-hpd-with-enabled-mode: - shard-rkl: NOTRUN -> [SKIP][107] ([i915#7828]) +5 other tests skip [107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_chamelium_hpd@hdmi-hpd-with-enabled-mode.html * igt@kms_content_protection@dp-mst-lic-type-0: - shard-mtlp: NOTRUN -> [SKIP][108] ([i915#3299]) +1 other test skip [108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_content_protection@dp-mst-lic-type-0.html * igt@kms_content_protection@dp-mst-lic-type-1: - shard-dg1: NOTRUN -> [SKIP][109] ([i915#3299]) [109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_content_protection@dp-mst-lic-type-1.html * igt@kms_content_protection@srm@pipe-a-dp-4: - shard-dg2: NOTRUN -> [TIMEOUT][110] ([i915#7173]) [110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-11/igt@kms_content_protection@srm@pipe-a-dp-4.html * igt@kms_content_protection@type1: - shard-rkl: NOTRUN -> [SKIP][111] ([i915#7118] / [i915#9424]) [111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_content_protection@type1.html * igt@kms_content_protection@uevent: - shard-tglu: NOTRUN -> [SKIP][112] ([i915#6944] / [i915#7116] / [i915#7118] / [i915#9424]) [112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_content_protection@uevent.html * igt@kms_cursor_crc@cursor-onscreen-256x85: - shard-mtlp: NOTRUN -> [SKIP][113] ([i915#8814]) +1 other test skip [113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-7/igt@kms_cursor_crc@cursor-onscreen-256x85.html * igt@kms_cursor_crc@cursor-onscreen-512x512: - shard-tglu: NOTRUN -> [SKIP][114] ([i915#11453]) +1 other test skip [114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_cursor_crc@cursor-onscreen-512x512.html * igt@kms_cursor_crc@cursor-random-32x10: - shard-dg2: NOTRUN -> [SKIP][115] ([i915#3555]) +2 other tests skip [115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_cursor_crc@cursor-random-32x10.html * igt@kms_cursor_crc@cursor-random-512x512: - shard-dg1: NOTRUN -> [SKIP][116] ([i915#11453]) +1 other test skip [116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_cursor_crc@cursor-random-512x512.html * igt@kms_cursor_crc@cursor-sliding-max-size: - shard-rkl: NOTRUN -> [SKIP][117] ([i915#3555]) [117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_cursor_crc@cursor-sliding-max-size.html * igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy: - shard-rkl: NOTRUN -> [SKIP][118] +12 other tests skip [118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy.html * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy: - shard-dg1: NOTRUN -> [SKIP][119] ([i915#4103] / [i915#4213]) +1 other test skip [119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html * igt@kms_cursor_legacy@cursora-vs-flipb-atomic-transitions-varying-size: - shard-mtlp: NOTRUN -> [SKIP][120] ([i915#9809]) [120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@kms_cursor_legacy@cursora-vs-flipb-atomic-transitions-varying-size.html * igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions: - shard-mtlp: NOTRUN -> [SKIP][121] +8 other tests skip [121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions.html * igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions: - shard-mtlp: NOTRUN -> [SKIP][122] ([i915#4213]) [122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions.html * igt@kms_dirtyfb@drrs-dirtyfb-ioctl: - shard-mtlp: NOTRUN -> [SKIP][123] ([i915#9833]) [123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@kms_dirtyfb@drrs-dirtyfb-ioctl.html * igt@kms_dsc@dsc-fractional-bpp: - shard-dg2: NOTRUN -> [SKIP][124] ([i915#3840] / [i915#9688]) [124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_dsc@dsc-fractional-bpp.html * igt@kms_dsc@dsc-fractional-bpp-with-bpc: - shard-mtlp: NOTRUN -> [SKIP][125] ([i915#3840]) [125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@kms_dsc@dsc-fractional-bpp-with-bpc.html * igt@kms_dsc@dsc-with-bpc: - shard-dg1: NOTRUN -> [SKIP][126] ([i915#3555] / [i915#3840]) [126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_dsc@dsc-with-bpc.html * igt@kms_dsc@dsc-with-formats: - shard-rkl: NOTRUN -> [SKIP][127] ([i915#3555] / [i915#3840]) [127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_dsc@dsc-with-formats.html * igt@kms_feature_discovery@chamelium: - shard-dg1: NOTRUN -> [SKIP][128] ([i915#4854]) [128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_feature_discovery@chamelium.html * igt@kms_fence_pin_leak: - shard-mtlp: NOTRUN -> [SKIP][129] ([i915#4881]) [129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_fence_pin_leak.html * igt@kms_flip@2x-dpms-vs-vblank-race: - shard-dg2: NOTRUN -> [SKIP][130] +6 other tests skip [130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_flip@2x-dpms-vs-vblank-race.html * igt@kms_flip@2x-flip-vs-dpms: - shard-tglu: NOTRUN -> [SKIP][131] ([i915#3637]) +2 other tests skip [131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_flip@2x-flip-vs-dpms.html * igt@kms_flip@2x-plain-flip-interruptible: - shard-dg1: NOTRUN -> [SKIP][132] ([i915#9934]) +2 other tests skip [132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_flip@2x-plain-flip-interruptible.html * igt@kms_flip@2x-wf_vblank-ts-check-interruptible: - shard-mtlp: NOTRUN -> [SKIP][133] ([i915#3637]) [133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@kms_flip@2x-wf_vblank-ts-check-interruptible.html * igt@kms_flip@flip-vs-fences: - shard-dg1: NOTRUN -> [SKIP][134] ([i915#8381]) [134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_flip@flip-vs-fences.html * igt@kms_flip@flip-vs-fences-interruptible: - shard-mtlp: NOTRUN -> [SKIP][135] ([i915#8381]) [135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_flip@flip-vs-fences-interruptible.html * igt@kms_flip@plain-flip-ts-check: - shard-rkl: [PASS][136] -> [FAIL][137] ([i915#2122]) [136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-rkl-3/igt@kms_flip@plain-flip-ts-check.html [137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-5/igt@kms_flip@plain-flip-ts-check.html - shard-dg1: [PASS][138] -> [FAIL][139] ([i915#2122]) [138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg1-13/igt@kms_flip@plain-flip-ts-check.html [139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_flip@plain-flip-ts-check.html * igt@kms_flip@plain-flip-ts-check@a-hdmi-a4: - shard-dg1: NOTRUN -> [FAIL][140] ([i915#2122]) +1 other test fail [140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_flip@plain-flip-ts-check@a-hdmi-a4.html * igt@kms_flip@plain-flip-ts-check@b-hdmi-a2: - shard-rkl: [PASS][141] -> [FAIL][142] ([i915#11989]) +1 other test fail [141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-rkl-3/igt@kms_flip@plain-flip-ts-check@b-hdmi-a2.html [142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-5/igt@kms_flip@plain-flip-ts-check@b-hdmi-a2.html * igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-upscaling: - shard-tglu: NOTRUN -> [SKIP][143] ([i915#2672] / [i915#3555]) [143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-upscaling.html * igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-upscaling@pipe-a-valid-mode: - shard-tglu: NOTRUN -> [SKIP][144] ([i915#2587] / [i915#2672]) [144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-upscaling@pipe-a-valid-mode.html * igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-upscaling: - shard-dg1: NOTRUN -> [SKIP][145] ([i915#2672] / [i915#3555]) [145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-upscaling.html * igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-upscaling@pipe-a-valid-mode: - shard-dg1: NOTRUN -> [SKIP][146] ([i915#2587] / [i915#2672]) [146]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-upscaling@pipe-a-valid-mode.html * igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-upscaling: - shard-mtlp: NOTRUN -> [SKIP][147] ([i915#2672] / [i915#3555] / [i915#8813]) +2 other tests skip [147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-upscaling.html * igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling@pipe-a-valid-mode: - shard-rkl: NOTRUN -> [SKIP][148] ([i915#2672]) +2 other tests skip [148]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling@pipe-a-valid-mode.html * igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling@pipe-a-default-mode: - shard-mtlp: NOTRUN -> [SKIP][149] ([i915#2672]) +2 other tests skip [149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling@pipe-a-default-mode.html * igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-32bpp-yftile-downscaling: - shard-rkl: NOTRUN -> [SKIP][150] ([i915#2672] / [i915#3555]) +2 other tests skip [150]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-32bpp-yftile-downscaling.html * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling: - shard-dg2: NOTRUN -> [SKIP][151] ([i915#2672] / [i915#3555] / [i915#5190]) +1 other test skip [151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling.html * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling@pipe-a-valid-mode: - shard-dg2: NOTRUN -> [SKIP][152] ([i915#2672]) +1 other test skip [152]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling@pipe-a-valid-mode.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-gtt: - shard-mtlp: NOTRUN -> [SKIP][153] ([i915#8708]) +3 other tests skip [153]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-gtt.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-gtt: - shard-dg1: NOTRUN -> [SKIP][154] ([i915#8708]) +10 other tests skip [154]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-gtt.html * igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-mmap-cpu: - shard-dg1: NOTRUN -> [SKIP][155] +33 other tests skip [155]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-mmap-cpu.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-pri-indfb-multidraw: - shard-dg1: NOTRUN -> [SKIP][156] ([i915#3458]) +13 other tests skip [156]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_frontbuffer_tracking@fbcpsr-1p-pri-indfb-multidraw.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-render: - shard-dg2: NOTRUN -> [SKIP][157] ([i915#3458]) +4 other tests skip [157]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-render.html * igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-mmap-gtt: - shard-tglu: NOTRUN -> [SKIP][158] +16 other tests skip [158]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-mmap-gtt.html * igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-shrfb-pgflip-blt: - shard-dg2: NOTRUN -> [SKIP][159] ([i915#5354]) +7 other tests skip [159]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-3/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-shrfb-pgflip-blt.html * igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-blt: - shard-mtlp: NOTRUN -> [SKIP][160] ([i915#1825]) +13 other tests skip [160]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-blt.html * igt@kms_frontbuffer_tracking@fbcpsr-rgb565-draw-mmap-gtt: - shard-rkl: NOTRUN -> [SKIP][161] ([i915#3023]) +12 other tests skip [161]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_frontbuffer_tracking@fbcpsr-rgb565-draw-mmap-gtt.html * igt@kms_frontbuffer_tracking@fbcpsr-tiling-4: - shard-dg1: NOTRUN -> [SKIP][162] ([i915#5439]) [162]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_frontbuffer_tracking@fbcpsr-tiling-4.html * igt@kms_frontbuffer_tracking@psr-2p-scndscrn-indfb-msflip-blt: - shard-rkl: NOTRUN -> [SKIP][163] ([i915#1825]) +18 other tests skip [163]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-indfb-msflip-blt.html * igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-wc: - shard-dg2: NOTRUN -> [SKIP][164] ([i915#8708]) +3 other tests skip [164]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-wc.html * igt@kms_hdr@invalid-hdr: - shard-dg2: NOTRUN -> [SKIP][165] ([i915#3555] / [i915#8228]) [165]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_hdr@invalid-hdr.html * igt@kms_hdr@static-toggle-dpms: - shard-rkl: NOTRUN -> [SKIP][166] ([i915#3555] / [i915#8228]) +1 other test skip [166]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_hdr@static-toggle-dpms.html * igt@kms_hdr@static-toggle-suspend: - shard-dg2: [PASS][167] -> [SKIP][168] ([i915#3555] / [i915#8228]) [167]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-11/igt@kms_hdr@static-toggle-suspend.html [168]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_hdr@static-toggle-suspend.html * igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format: - shard-dg1: NOTRUN -> [SKIP][169] ([i915#12247]) +8 other tests skip [169]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format.html * igt@kms_plane_scaling@plane-downscale-factor-0-25-with-rotation@pipe-b: - shard-mtlp: NOTRUN -> [SKIP][170] ([i915#12247]) +4 other tests skip [170]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@kms_plane_scaling@plane-downscale-factor-0-25-with-rotation@pipe-b.html * igt@kms_plane_scaling@planes-downscale-factor-0-25-unity-scaling@pipe-d: - shard-tglu: NOTRUN -> [SKIP][171] ([i915#12247]) +4 other tests skip [171]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_plane_scaling@planes-downscale-factor-0-25-unity-scaling@pipe-d.html * igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-20x20: - shard-dg2: NOTRUN -> [SKIP][172] ([i915#12247] / [i915#9423]) [172]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-20x20.html * igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-20x20@pipe-b: - shard-dg2: NOTRUN -> [SKIP][173] ([i915#12247]) +3 other tests skip [173]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-20x20@pipe-b.html * igt@kms_plane_scaling@planes-downscale-factor-0-5-upscale-20x20@pipe-b: - shard-glk: NOTRUN -> [SKIP][174] +75 other tests skip [174]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-glk8/igt@kms_plane_scaling@planes-downscale-factor-0-5-upscale-20x20@pipe-b.html * igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-25: - shard-rkl: NOTRUN -> [SKIP][175] ([i915#6953]) [175]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-25.html * igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-25@pipe-b: - shard-rkl: NOTRUN -> [SKIP][176] ([i915#12247]) +1 other test skip [176]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-25@pipe-b.html * igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-25: - shard-dg1: NOTRUN -> [SKIP][177] ([i915#3555]) +5 other tests skip [177]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-25.html * igt@kms_pm_backlight@fade-with-suspend: - shard-rkl: NOTRUN -> [SKIP][178] ([i915#5354]) [178]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_pm_backlight@fade-with-suspend.html * igt@kms_pm_dc@dc3co-vpb-simulation: - shard-rkl: NOTRUN -> [SKIP][179] ([i915#9685]) [179]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_pm_dc@dc3co-vpb-simulation.html * igt@kms_pm_dc@dc6-dpms: - shard-tglu: NOTRUN -> [FAIL][180] ([i915#9295]) [180]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_pm_dc@dc6-dpms.html * igt@kms_pm_dc@dc9-dpms: - shard-tglu: [PASS][181] -> [SKIP][182] ([i915#4281]) [181]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-tglu-3/igt@kms_pm_dc@dc9-dpms.html [182]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_pm_dc@dc9-dpms.html * igt@kms_pm_rpm@dpms-mode-unset-non-lpsp: - shard-rkl: NOTRUN -> [SKIP][183] ([i915#9519]) [183]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_pm_rpm@dpms-mode-unset-non-lpsp.html * igt@kms_pm_rpm@modeset-non-lpsp-stress-no-wait: - shard-dg2: [PASS][184] -> [SKIP][185] ([i915#9519]) +1 other test skip [184]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-1/igt@kms_pm_rpm@modeset-non-lpsp-stress-no-wait.html [185]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-2/igt@kms_pm_rpm@modeset-non-lpsp-stress-no-wait.html * igt@kms_prime@d3hot: - shard-dg1: NOTRUN -> [SKIP][186] ([i915#6524]) [186]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_prime@d3hot.html * igt@kms_psr2_sf@fbc-cursor-plane-update-sf: - shard-rkl: NOTRUN -> [SKIP][187] ([i915#11520]) [187]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_psr2_sf@fbc-cursor-plane-update-sf.html * igt@kms_psr2_sf@fbc-overlay-plane-move-continuous-exceed-sf: - shard-tglu: NOTRUN -> [SKIP][188] ([i915#11520]) +1 other test skip [188]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_psr2_sf@fbc-overlay-plane-move-continuous-exceed-sf.html * igt@kms_psr2_sf@fbc-overlay-primary-update-sf-dmg-area: - shard-dg2: NOTRUN -> [SKIP][189] ([i915#11520]) [189]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_psr2_sf@fbc-overlay-primary-update-sf-dmg-area.html * igt@kms_psr2_sf@plane-move-sf-dmg-area: - shard-dg1: NOTRUN -> [SKIP][190] ([i915#11520]) +1 other test skip [190]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_psr2_sf@plane-move-sf-dmg-area.html * igt@kms_psr2_su@page_flip-nv12: - shard-rkl: NOTRUN -> [SKIP][191] ([i915#9683]) [191]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_psr2_su@page_flip-nv12.html * igt@kms_psr2_su@page_flip-xrgb8888: - shard-dg1: NOTRUN -> [SKIP][192] ([i915#9683]) [192]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_psr2_su@page_flip-xrgb8888.html * igt@kms_psr@fbc-pr-sprite-mmap-gtt: - shard-dg2: NOTRUN -> [SKIP][193] ([i915#1072] / [i915#9732]) +5 other tests skip [193]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_psr@fbc-pr-sprite-mmap-gtt.html * igt@kms_psr@fbc-psr2-cursor-plane-move: - shard-snb: NOTRUN -> [SKIP][194] +6 other tests skip [194]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-snb2/igt@kms_psr@fbc-psr2-cursor-plane-move.html - shard-mtlp: NOTRUN -> [SKIP][195] ([i915#9688]) +7 other tests skip [195]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-7/igt@kms_psr@fbc-psr2-cursor-plane-move.html * igt@kms_psr@pr-primary-mmap-gtt: - shard-dg1: NOTRUN -> [SKIP][196] ([i915#1072] / [i915#9732]) +14 other tests skip [196]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-15/igt@kms_psr@pr-primary-mmap-gtt.html * igt@kms_psr@pr-sprite-mmap-cpu: - shard-tglu: NOTRUN -> [SKIP][197] ([i915#9732]) +5 other tests skip [197]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_psr@pr-sprite-mmap-cpu.html * igt@kms_psr@psr-cursor-render: - shard-rkl: NOTRUN -> [SKIP][198] ([i915#1072] / [i915#9732]) +10 other tests skip [198]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_psr@psr-cursor-render.html * igt@kms_psr@psr-sprite-mmap-gtt@edp-1: - shard-mtlp: NOTRUN -> [SKIP][199] ([i915#4077] / [i915#9688]) +1 other test skip [199]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@kms_psr@psr-sprite-mmap-gtt@edp-1.html * igt@kms_psr_stress_test@flip-primary-invalidate-overlay: - shard-dg1: NOTRUN -> [SKIP][200] ([i915#9685]) [200]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html * igt@kms_rotation_crc@bad-pixel-format: - shard-mtlp: NOTRUN -> [SKIP][201] ([i915#4235]) [201]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@kms_rotation_crc@bad-pixel-format.html * igt@kms_rotation_crc@primary-y-tiled-reflect-x-180: - shard-mtlp: NOTRUN -> [SKIP][202] ([i915#5289]) [202]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@kms_rotation_crc@primary-y-tiled-reflect-x-180.html * igt@kms_rotation_crc@primary-y-tiled-reflect-x-270: - shard-dg2: NOTRUN -> [SKIP][203] ([i915#11131] / [i915#5190]) [203]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_rotation_crc@primary-y-tiled-reflect-x-270.html * igt@kms_rotation_crc@primary-yf-tiled-reflect-x-0: - shard-rkl: NOTRUN -> [SKIP][204] ([i915#5289]) [204]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_rotation_crc@primary-yf-tiled-reflect-x-0.html * igt@kms_rotation_crc@primary-yf-tiled-reflect-x-270: - shard-tglu: NOTRUN -> [SKIP][205] ([i915#5289]) [205]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_rotation_crc@primary-yf-tiled-reflect-x-270.html * igt@kms_scaling_modes@scaling-mode-full: - shard-tglu: NOTRUN -> [SKIP][206] ([i915#3555]) +2 other tests skip [206]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@kms_scaling_modes@scaling-mode-full.html * igt@kms_universal_plane@cursor-fb-leak: - shard-rkl: [PASS][207] -> [FAIL][208] ([i915#9196]) [207]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-rkl-3/igt@kms_universal_plane@cursor-fb-leak.html [208]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-2/igt@kms_universal_plane@cursor-fb-leak.html * igt@kms_universal_plane@cursor-fb-leak@pipe-b-hdmi-a-1: - shard-tglu: [PASS][209] -> [FAIL][210] ([i915#9196]) +2 other tests fail [209]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-tglu-3/igt@kms_universal_plane@cursor-fb-leak@pipe-b-hdmi-a-1.html [210]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-3/igt@kms_universal_plane@cursor-fb-leak@pipe-b-hdmi-a-1.html - shard-rkl: NOTRUN -> [FAIL][211] ([i915#9196]) [211]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-2/igt@kms_universal_plane@cursor-fb-leak@pipe-b-hdmi-a-1.html * igt@kms_vrr@negative-basic: - shard-dg1: NOTRUN -> [SKIP][212] ([i915#3555] / [i915#9906]) [212]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_vrr@negative-basic.html * igt@kms_vrr@seamless-rr-switch-drrs: - shard-rkl: NOTRUN -> [SKIP][213] ([i915#9906]) [213]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_vrr@seamless-rr-switch-drrs.html * igt@kms_writeback@writeback-fb-id: - shard-dg2: NOTRUN -> [SKIP][214] ([i915#2437]) [214]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_writeback@writeback-fb-id.html * igt@kms_writeback@writeback-fb-id-xrgb2101010: - shard-dg1: NOTRUN -> [SKIP][215] ([i915#2437] / [i915#9412]) [215]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@kms_writeback@writeback-fb-id-xrgb2101010.html * igt@perf_pmu@busy-double-start@vecs1: - shard-dg2: NOTRUN -> [FAIL][216] ([i915#4349]) +4 other tests fail [216]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@perf_pmu@busy-double-start@vecs1.html * igt@perf_pmu@cpu-hotplug: - shard-mtlp: NOTRUN -> [SKIP][217] ([i915#8850]) [217]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@perf_pmu@cpu-hotplug.html * igt@perf_pmu@semaphore-busy@bcs0: - shard-mtlp: [PASS][218] -> [FAIL][219] ([i915#4349]) +1 other test fail [218]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-mtlp-5/igt@perf_pmu@semaphore-busy@bcs0.html [219]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@perf_pmu@semaphore-busy@bcs0.html * igt@prime_vgem@coherency-gtt: - shard-dg1: NOTRUN -> [SKIP][220] ([i915#3708] / [i915#4077]) +1 other test skip [220]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@prime_vgem@coherency-gtt.html * igt@prime_vgem@fence-flip-hang: - shard-dg1: NOTRUN -> [SKIP][221] ([i915#3708]) +1 other test skip [221]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@prime_vgem@fence-flip-hang.html * igt@prime_vgem@fence-read-hang: - shard-rkl: NOTRUN -> [SKIP][222] ([i915#3708]) [222]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@prime_vgem@fence-read-hang.html * igt@sriov_basic@enable-vfs-autoprobe-on: - shard-dg1: NOTRUN -> [SKIP][223] ([i915#9917]) [223]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-16/igt@sriov_basic@enable-vfs-autoprobe-on.html * igt@syncobj_wait@invalid-wait-zero-handles: - shard-rkl: NOTRUN -> [FAIL][224] ([i915#9781]) [224]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@syncobj_wait@invalid-wait-zero-handles.html #### Possible fixes #### * igt@drm_fdinfo@idle@rcs0: - shard-rkl: [FAIL][225] ([i915#7742]) -> [PASS][226] +1 other test pass [225]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-rkl-3/igt@drm_fdinfo@idle@rcs0.html [226]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-5/igt@drm_fdinfo@idle@rcs0.html * igt@gem_exec_endless@dispatch: - shard-dg2: [TIMEOUT][227] ([i915#7016]) -> [PASS][228] [227]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-11/igt@gem_exec_endless@dispatch.html [228]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-3/igt@gem_exec_endless@dispatch.html * igt@gem_exec_endless@dispatch@bcs0: - shard-dg2: [TIMEOUT][229] ([i915#3778] / [i915#7016]) -> [PASS][230] [229]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-11/igt@gem_exec_endless@dispatch@bcs0.html [230]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-3/igt@gem_exec_endless@dispatch@bcs0.html * igt@gem_exec_fair@basic-pace-share@rcs0: - shard-rkl: [FAIL][231] ([i915#2842]) -> [PASS][232] +1 other test pass [231]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-rkl-6/igt@gem_exec_fair@basic-pace-share@rcs0.html [232]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-3/igt@gem_exec_fair@basic-pace-share@rcs0.html - shard-tglu: [FAIL][233] ([i915#2842]) -> [PASS][234] +1 other test pass [233]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-tglu-5/igt@gem_exec_fair@basic-pace-share@rcs0.html [234]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-5/igt@gem_exec_fair@basic-pace-share@rcs0.html * igt@i915_pm_rc6_residency@rc6-idle@gt0-vecs0: - shard-dg1: [FAIL][235] ([i915#3591]) -> [PASS][236] +2 other tests pass [235]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg1-16/igt@i915_pm_rc6_residency@rc6-idle@gt0-vecs0.html [236]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-13/igt@i915_pm_rc6_residency@rc6-idle@gt0-vecs0.html * igt@i915_selftest@live@workarounds: - shard-mtlp: [ABORT][237] ([i915#12061]) -> [PASS][238] +1 other test pass [237]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-mtlp-3/igt@i915_selftest@live@workarounds.html [238]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-6/igt@i915_selftest@live@workarounds.html * igt@kms_atomic_transition@plane-all-modeset-transition-internal-panels@pipe-a-edp-1: - shard-mtlp: [FAIL][239] ([i915#11808] / [i915#5956]) -> [PASS][240] +1 other test pass [239]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-mtlp-6/igt@kms_atomic_transition@plane-all-modeset-transition-internal-panels@pipe-a-edp-1.html [240]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-5/igt@kms_atomic_transition@plane-all-modeset-transition-internal-panels@pipe-a-edp-1.html * igt@kms_atomic_transition@plane-all-modeset-transition@pipe-a-hdmi-a-1: - shard-snb: [FAIL][241] ([i915#5956]) -> [PASS][242] +1 other test pass [241]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-snb5/igt@kms_atomic_transition@plane-all-modeset-transition@pipe-a-hdmi-a-1.html [242]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-snb6/igt@kms_atomic_transition@plane-all-modeset-transition@pipe-a-hdmi-a-1.html - shard-tglu: [FAIL][243] ([i915#11808]) -> [PASS][244] +1 other test pass [243]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-tglu-7/igt@kms_atomic_transition@plane-all-modeset-transition@pipe-a-hdmi-a-1.html [244]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-8/igt@kms_atomic_transition@plane-all-modeset-transition@pipe-a-hdmi-a-1.html * igt@kms_cursor_legacy@torture-bo: - shard-tglu: [DMESG-WARN][245] ([i915#10166] / [i915#1982]) -> [PASS][246] [245]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-tglu-9/igt@kms_cursor_legacy@torture-bo.html [246]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-7/igt@kms_cursor_legacy@torture-bo.html * igt@kms_cursor_legacy@torture-bo@pipe-a: - shard-tglu: [DMESG-WARN][247] ([i915#10166]) -> [PASS][248] [247]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-tglu-9/igt@kms_cursor_legacy@torture-bo@pipe-a.html [248]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-7/igt@kms_cursor_legacy@torture-bo@pipe-a.html * igt@kms_dither@fb-8bpc-vs-panel-6bpc: - shard-dg2: [SKIP][249] ([i915#3555]) -> [PASS][250] [249]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-6/igt@kms_dither@fb-8bpc-vs-panel-6bpc.html [250]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-11/igt@kms_dither@fb-8bpc-vs-panel-6bpc.html * igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-blt: - shard-dg2: [FAIL][251] ([i915#6880]) -> [PASS][252] [251]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-2/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-blt.html [252]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-7/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-blt.html * igt@kms_hdr@invalid-metadata-sizes: - shard-dg2: [SKIP][253] ([i915#3555] / [i915#8228]) -> [PASS][254] [253]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-6/igt@kms_hdr@invalid-metadata-sizes.html [254]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-11/igt@kms_hdr@invalid-metadata-sizes.html * igt@kms_pm_rpm@modeset-lpsp-stress: - shard-dg2: [SKIP][255] ([i915#9519]) -> [PASS][256] +2 other tests pass [255]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-1/igt@kms_pm_rpm@modeset-lpsp-stress.html [256]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-2/igt@kms_pm_rpm@modeset-lpsp-stress.html * igt@kms_pm_rpm@modeset-lpsp-stress-no-wait: - shard-rkl: [SKIP][257] ([i915#9519]) -> [PASS][258] [257]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-rkl-3/igt@kms_pm_rpm@modeset-lpsp-stress-no-wait.html [258]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-4/igt@kms_pm_rpm@modeset-lpsp-stress-no-wait.html * igt@kms_selftest@drm_framebuffer: - shard-rkl: [ABORT][259] ([i915#12231]) -> [PASS][260] [259]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-rkl-1/igt@kms_selftest@drm_framebuffer.html [260]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-5/igt@kms_selftest@drm_framebuffer.html - shard-dg1: [ABORT][261] ([i915#12231]) -> [PASS][262] [261]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg1-18/igt@kms_selftest@drm_framebuffer.html [262]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-18/igt@kms_selftest@drm_framebuffer.html - shard-snb: [ABORT][263] ([i915#12231]) -> [PASS][264] [263]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-snb6/igt@kms_selftest@drm_framebuffer.html [264]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-snb2/igt@kms_selftest@drm_framebuffer.html - shard-tglu: [ABORT][265] ([i915#12231]) -> [PASS][266] [265]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-tglu-3/igt@kms_selftest@drm_framebuffer.html [266]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-7/igt@kms_selftest@drm_framebuffer.html - shard-mtlp: [ABORT][267] ([i915#12231]) -> [PASS][268] [267]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-mtlp-4/igt@kms_selftest@drm_framebuffer.html [268]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-7/igt@kms_selftest@drm_framebuffer.html - shard-glk: [ABORT][269] ([i915#12231]) -> [PASS][270] [269]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-glk1/igt@kms_selftest@drm_framebuffer.html [270]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-glk7/igt@kms_selftest@drm_framebuffer.html - shard-dg2: [ABORT][271] ([i915#12231]) -> [PASS][272] [271]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-5/igt@kms_selftest@drm_framebuffer.html [272]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-3/igt@kms_selftest@drm_framebuffer.html * igt@kms_universal_plane@cursor-fb-leak: - shard-dg1: [FAIL][273] ([i915#9196]) -> [PASS][274] +1 other test pass [273]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg1-14/igt@kms_universal_plane@cursor-fb-leak.html [274]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg1-18/igt@kms_universal_plane@cursor-fb-leak.html * igt@kms_universal_plane@cursor-fb-leak@pipe-b-hdmi-a-3: - shard-dg2: [FAIL][275] ([i915#9196]) -> [PASS][276] +1 other test pass [275]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-5/igt@kms_universal_plane@cursor-fb-leak@pipe-b-hdmi-a-3.html [276]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-6/igt@kms_universal_plane@cursor-fb-leak@pipe-b-hdmi-a-3.html * igt@perf_pmu@busy-double-start@bcs0: - shard-mtlp: [FAIL][277] ([i915#4349]) -> [PASS][278] [277]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-mtlp-2/igt@perf_pmu@busy-double-start@bcs0.html [278]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-4/igt@perf_pmu@busy-double-start@bcs0.html #### Warnings #### * igt@gem_exec_big@single: - shard-tglu: [ABORT][279] -> [ABORT][280] ([i915#11713]) [279]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-tglu-3/igt@gem_exec_big@single.html [280]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-tglu-9/igt@gem_exec_big@single.html * igt@i915_module_load@reload-with-fault-injection: - shard-mtlp: [ABORT][281] ([i915#10887] / [i915#11231]) -> [ABORT][282] ([i915#10131] / [i915#9697]) [281]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-mtlp-6/igt@i915_module_load@reload-with-fault-injection.html [282]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-7/igt@i915_module_load@reload-with-fault-injection.html * igt@kms_big_fb@4-tiled-8bpp-rotate-90: - shard-mtlp: [ABORT][283] ([i915#10354]) -> [SKIP][284] [283]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-mtlp-8/igt@kms_big_fb@4-tiled-8bpp-rotate-90.html [284]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-mtlp-2/igt@kms_big_fb@4-tiled-8bpp-rotate-90.html * igt@kms_content_protection@srm: - shard-dg2: [SKIP][285] ([i915#7118]) -> [TIMEOUT][286] ([i915#7173]) [285]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-8/igt@kms_content_protection@srm.html [286]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-11/igt@kms_content_protection@srm.html * igt@kms_cursor_crc@cursor-offscreen-512x170: - shard-dg2: [SKIP][287] ([i915#11453] / [i915#3359]) -> [SKIP][288] ([i915#11453]) [287]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-11/igt@kms_cursor_crc@cursor-offscreen-512x170.html [288]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-3/igt@kms_cursor_crc@cursor-offscreen-512x170.html * igt@kms_cursor_crc@cursor-random-512x170: - shard-dg2: [SKIP][289] ([i915#11453]) -> [SKIP][290] ([i915#11453] / [i915#3359]) +1 other test skip [289]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-6/igt@kms_cursor_crc@cursor-random-512x170.html [290]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-11/igt@kms_cursor_crc@cursor-random-512x170.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-pwrite: - shard-dg2: [SKIP][291] ([i915#3458]) -> [SKIP][292] ([i915#10433] / [i915#3458]) [291]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-3/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-pwrite.html [292]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-4/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-pwrite.html * igt@kms_frontbuffer_tracking@fbcpsr-indfb-scaledprimary: - shard-dg2: [SKIP][293] ([i915#10433] / [i915#3458]) -> [SKIP][294] ([i915#3458]) [293]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-4/igt@kms_frontbuffer_tracking@fbcpsr-indfb-scaledprimary.html [294]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_frontbuffer_tracking@fbcpsr-indfb-scaledprimary.html * igt@kms_multipipe_modeset@basic-max-pipe-crc-check: - shard-rkl: [SKIP][295] ([i915#4816]) -> [SKIP][296] ([i915#4070] / [i915#4816]) [295]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-rkl-3/igt@kms_multipipe_modeset@basic-max-pipe-crc-check.html [296]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-rkl-5/igt@kms_multipipe_modeset@basic-max-pipe-crc-check.html * igt@kms_psr@pr-cursor-mmap-cpu: - shard-dg2: [SKIP][297] ([i915#1072] / [i915#9673] / [i915#9732]) -> [SKIP][298] ([i915#1072] / [i915#9732]) +9 other tests skip [297]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-11/igt@kms_psr@pr-cursor-mmap-cpu.html [298]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-8/igt@kms_psr@pr-cursor-mmap-cpu.html * igt@kms_psr@psr-cursor-mmap-cpu: - shard-dg2: [SKIP][299] ([i915#1072] / [i915#9732]) -> [SKIP][300] ([i915#1072] / [i915#9673] / [i915#9732]) +15 other tests skip [299]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-8/igt@kms_psr@psr-cursor-mmap-cpu.html [300]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-11/igt@kms_psr@psr-cursor-mmap-cpu.html * igt@perf@non-zero-reason@0-rcs0: - shard-dg2: [FAIL][301] ([i915#7484]) -> [FAIL][302] ([i915#9100]) +1 other test fail [301]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15429/shard-dg2-8/igt@perf@non-zero-reason@0-rcs0.html [302]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/shard-dg2-7/igt@perf@non-zero-reason@0-rcs0.html [i915#10131]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10131 [i915#10166]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10166 [i915#10307]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10307 [i915#10354]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10354 [i915#10433]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10433 [i915#10434]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10434 [i915#10656]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10656 [i915#1072]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1072 [i915#10887]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10887 [i915#11131]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11131 [i915#11231]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11231 [i915#11453]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11453 [i915#11520]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11520 [i915#11681]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11681 [i915#11713]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11713 [i915#11808]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11808 [i915#11814]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11814 [i915#11815]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11815 [i915#11859]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11859 [i915#11989]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11989 [i915#12027]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12027 [i915#12042]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12042 [i915#12061]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061 [i915#12231]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12231 [i915#12238]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12238 [i915#12247]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12247 [i915#1769]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1769 [i915#1825]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1825 [i915#1982]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1982 [i915#2122]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2122 [i915#2437]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2437 [i915#2527]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2527 [i915#2587]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2587 [i915#2672]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2672 [i915#280]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/280 [i915#2842]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2842 [i915#2856]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2856 [i915#3023]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3023 [i915#3281]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3281 [i915#3282]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3282 [i915#3297]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3297 [i915#3299]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3299 [i915#3359]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3359 [i915#3458]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3458 [i915#3539]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3539 [i915#3555]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3555 [i915#3591]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3591 [i915#3637]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3637 [i915#3638]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3638 [i915#3708]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3708 [i915#3742]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3742 [i915#3778]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3778 [i915#3840]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3840 [i915#4070]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4070 [i915#4077]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4077 [i915#4083]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4083 [i915#4103]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4103 [i915#4213]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4213 [i915#4235]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4235 [i915#4270]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4270 [i915#4281]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4281 [i915#4349]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4349 [i915#4538]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4538 [i915#4613]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4613 [i915#4771]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4771 [i915#4812]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4812 [i915#4816]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4816 [i915#4852]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4852 [i915#4854]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4854 [i915#4873]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4873 [i915#4880]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4880 [i915#4881]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4881 [i915#5190]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5190 [i915#5286]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5286 [i915#5289]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5289 [i915#5354]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5354 [i915#5439]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5439 [i915#5956]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5956 [i915#6095]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6095 [i915#6412]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6412 [i915#6524]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6524 [i915#6621]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6621 [i915#6645]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6645 [i915#6880]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6880 [i915#6944]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6944 [i915#6953]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6953 [i915#7016]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7016 [i915#7116]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7116 [i915#7118]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7118 [i915#7173]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7173 [i915#7213]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7213 [i915#7276]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7276 [i915#7297]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7297 [i915#7484]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7484 [i915#7707]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7707 [i915#7742]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7742 [i915#7828]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7828 [i915#8228]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8228 [i915#8381]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8381 [i915#8399]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8399 [i915#8411]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8411 [i915#8414]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8414 [i915#8428]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8428 [i915#8555]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8555 [i915#8708]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8708 [i915#8709]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8709 [i915#8813]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8813 [i915#8814]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8814 [i915#8850]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8850 [i915#9100]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9100 [i915#9196]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9196 [i915#9295]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9295 [i915#9311]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9311 [i915#9323]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9323 [i915#9412]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9412 [i915#9423]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9423 [i915#9424]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9424 [i915#9519]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9519 [i915#9673]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9673 [i915#9683]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9683 [i915#9685]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9685 [i915#9688]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9688 [i915#9697]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9697 [i915#9732]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9732 [i915#9781]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9781 [i915#9809]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9809 [i915#9820]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9820 [i915#9833]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9833 [i915#9906]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9906 [i915#9917]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9917 [i915#9934]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9934 Build changes ------------- * Linux: CI_DRM_15429 -> Patchwork_138782v1 CI-20190529: 20190529 CI_DRM_15429: 38e1b615fb395b928e514108e908cd6edf3d34c3 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_8022: 2d82f767a959d58c04ff3876d59d67924208d4ef @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_138782v1: 38e1b615fb395b928e514108e908cd6edf3d34c3 @ git://anongit.freedesktop.org/gfx-ci/linux piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138782v1/index.html [-- Attachment #2: Type: text/html, Size: 101451 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-17 17:43 [PATCH 0/2] drm: revert some framebuffer API tests Jani Nikula ` (4 preceding siblings ...) 2024-09-18 8:44 ` ✗ Fi.CI.IGT: failure " Patchwork @ 2024-09-24 10:06 ` Simona Vetter 2024-09-24 11:54 ` Maxime Ripard 5 siblings, 1 reply; 24+ messages in thread From: Simona Vetter @ 2024-09-24 10:06 UTC (permalink / raw) To: Jani Nikula Cc: dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maxime Ripard, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote: > The tests consistently trigger WARNs in drm_framebuffer code. I'm not > sure what the point is with type of belts and suspenders tests. The > warnings *are* the way to flag erroneous API usage. > > Warnings in turn trigger failures in CI. Filtering the warnings are > error prone, and, crucially, would also filter actual errors in case the > kunit tests are not run. > > I acknowledge there may be complex test cases where you'd end up > triggering warnings somewhere deep, but these are not it. These are > simple. > > Revert the tests, back to the drawing board. Yeah I think long-term we might want a kunit framework so that we can catch dmesg warnings we expect and test for those, without those warnings actually going to dmesg. Similar to how the lockdep tests also reroute locking validation, so that the expected positive tests don't wreak lockdep for real. But until that exists, we can't have tests that splat in dmesg when they work as intended. Reviewed-by: Simona Vetter <simona.vetter@ffwll.ch> Cheers, Sima > > BR, > Jani. > > > Cc: Carlos Eduardo Gallo Filho <gcarlos@disroot.org> > Cc: Maxime Ripard <mripard@kernel.org> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> > Cc: Thomas Zimmermann <tzimmermann@suse.de> > Cc: Jeff Johnson <quic_jjohnson@quicinc.com> > > > Jani Nikula (2): > Revert "drm/tests: Add test for drm_framebuffer_free()" > Revert "drm/tests: Add test for drm_framebuffer_init()" > > drivers/gpu/drm/drm_framebuffer.c | 1 - > drivers/gpu/drm/drm_mode_object.c | 1 - > drivers/gpu/drm/tests/drm_framebuffer_test.c | 134 ------------------- > 3 files changed, 136 deletions(-) > > -- > 2.39.2 > -- Simona Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-24 10:06 ` [PATCH 0/2] " Simona Vetter @ 2024-09-24 11:54 ` Maxime Ripard 2024-09-24 13:37 ` Guenter Roeck 0 siblings, 1 reply; 24+ messages in thread From: Maxime Ripard @ 2024-09-24 11:54 UTC (permalink / raw) To: Simona Vetter, Guenter Roeck Cc: Jani Nikula, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson [-- Attachment #1: Type: text/plain, Size: 1388 bytes --] +Guenter On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: > On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote: > > The tests consistently trigger WARNs in drm_framebuffer code. I'm not > > sure what the point is with type of belts and suspenders tests. The > > warnings *are* the way to flag erroneous API usage. > > > > Warnings in turn trigger failures in CI. Filtering the warnings are > > error prone, and, crucially, would also filter actual errors in case the > > kunit tests are not run. > > > > I acknowledge there may be complex test cases where you'd end up > > triggering warnings somewhere deep, but these are not it. These are > > simple. > > > > Revert the tests, back to the drawing board. > > Yeah I think long-term we might want a kunit framework so that we can > catch dmesg warnings we expect and test for those, without those warnings > actually going to dmesg. Similar to how the lockdep tests also reroute > locking validation, so that the expected positive tests don't wreak > lockdep for real. > > But until that exists, we can't have tests that splat in dmesg when they > work as intended. It should be pretty soon: https://lore.kernel.org/dri-devel/20240403131936.787234-1-linux@roeck-us.net/ I'm not sure what happened to that series, but it looks like everybody was mostly happy with it? Maxime [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 273 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-24 11:54 ` Maxime Ripard @ 2024-09-24 13:37 ` Guenter Roeck 2024-09-24 13:56 ` Maxime Ripard 0 siblings, 1 reply; 24+ messages in thread From: Guenter Roeck @ 2024-09-24 13:37 UTC (permalink / raw) To: Maxime Ripard, Simona Vetter Cc: Jani Nikula, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On 9/24/24 04:54, Maxime Ripard wrote: > +Guenter > > On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: >> On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote: >>> The tests consistently trigger WARNs in drm_framebuffer code. I'm not >>> sure what the point is with type of belts and suspenders tests. The >>> warnings *are* the way to flag erroneous API usage. >>> >>> Warnings in turn trigger failures in CI. Filtering the warnings are >>> error prone, and, crucially, would also filter actual errors in case the >>> kunit tests are not run. >>> >>> I acknowledge there may be complex test cases where you'd end up >>> triggering warnings somewhere deep, but these are not it. These are >>> simple. >>> >>> Revert the tests, back to the drawing board. >> >> Yeah I think long-term we might want a kunit framework so that we can >> catch dmesg warnings we expect and test for those, without those warnings >> actually going to dmesg. Similar to how the lockdep tests also reroute >> locking validation, so that the expected positive tests don't wreak >> lockdep for real. >> >> But until that exists, we can't have tests that splat in dmesg when they >> work as intended. > > It should be pretty soon: > https://lore.kernel.org/dri-devel/20240403131936.787234-1-linux@roeck-us.net/ > > I'm not sure what happened to that series, but it looks like everybody > was mostly happy with it? > Major subsystem maintainers did not provide any feedback at all, and then there came the "it is not perfect enough" feedback, so I gave up on it. Guenter ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-24 13:37 ` Guenter Roeck @ 2024-09-24 13:56 ` Maxime Ripard 2024-09-24 15:09 ` Guenter Roeck 0 siblings, 1 reply; 24+ messages in thread From: Maxime Ripard @ 2024-09-24 13:56 UTC (permalink / raw) To: Guenter Roeck Cc: Simona Vetter, Jani Nikula, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson [-- Attachment #1: Type: text/plain, Size: 1892 bytes --] On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote: > On 9/24/24 04:54, Maxime Ripard wrote: > > +Guenter > > > > On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: > > > On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote: > > > > The tests consistently trigger WARNs in drm_framebuffer code. I'm not > > > > sure what the point is with type of belts and suspenders tests. The > > > > warnings *are* the way to flag erroneous API usage. > > > > > > > > Warnings in turn trigger failures in CI. Filtering the warnings are > > > > error prone, and, crucially, would also filter actual errors in case the > > > > kunit tests are not run. > > > > > > > > I acknowledge there may be complex test cases where you'd end up > > > > triggering warnings somewhere deep, but these are not it. These are > > > > simple. > > > > > > > > Revert the tests, back to the drawing board. > > > > > > Yeah I think long-term we might want a kunit framework so that we can > > > catch dmesg warnings we expect and test for those, without those warnings > > > actually going to dmesg. Similar to how the lockdep tests also reroute > > > locking validation, so that the expected positive tests don't wreak > > > lockdep for real. > > > > > > But until that exists, we can't have tests that splat in dmesg when they > > > work as intended. > > > > It should be pretty soon: > > https://lore.kernel.org/dri-devel/20240403131936.787234-1-linux@roeck-us.net/ > > > > I'm not sure what happened to that series, but it looks like everybody > > was mostly happy with it? > > > > Major subsystem maintainers did not provide any feedback at all, and then > there came the "it is not perfect enough" feedback, so I gave up on it. Well, if that means anything, we're interested even in something imperfect if it solves the above case :) Maxime [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 273 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-24 13:56 ` Maxime Ripard @ 2024-09-24 15:09 ` Guenter Roeck 2024-09-24 15:56 ` Jani Nikula 2024-09-25 11:52 ` Simona Vetter 0 siblings, 2 replies; 24+ messages in thread From: Guenter Roeck @ 2024-09-24 15:09 UTC (permalink / raw) To: Maxime Ripard Cc: Simona Vetter, Jani Nikula, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On 9/24/24 06:56, Maxime Ripard wrote: > On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote: >> On 9/24/24 04:54, Maxime Ripard wrote: >>> +Guenter >>> >>> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: >>>> On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote: >>>>> The tests consistently trigger WARNs in drm_framebuffer code. I'm not >>>>> sure what the point is with type of belts and suspenders tests. The >>>>> warnings *are* the way to flag erroneous API usage. >>>>> >>>>> Warnings in turn trigger failures in CI. Filtering the warnings are >>>>> error prone, and, crucially, would also filter actual errors in case the >>>>> kunit tests are not run. >>>>> >>>>> I acknowledge there may be complex test cases where you'd end up >>>>> triggering warnings somewhere deep, but these are not it. These are >>>>> simple. >>>>> >>>>> Revert the tests, back to the drawing board. >>>> >>>> Yeah I think long-term we might want a kunit framework so that we can >>>> catch dmesg warnings we expect and test for those, without those warnings >>>> actually going to dmesg. Similar to how the lockdep tests also reroute >>>> locking validation, so that the expected positive tests don't wreak >>>> lockdep for real. >>>> >>>> But until that exists, we can't have tests that splat in dmesg when they >>>> work as intended. >>> FWIW, that is arguable. More and more tests are added which do add such splats, and I don't see any hesitance by developers to adding more. So far I counted two alone in this commit window, and that does not include new splats from tests which I had already disabled. I simply disable those tests or don't enable them in the first place if they are new. I did the same with the drm unit tests due to the splats generated by the scaling unit tests, so any additional drm unit test splats don't make a difference for me since the tests are already disabled. >>> It should be pretty soon: >>> https://lore.kernel.org/dri-devel/20240403131936.787234-1-linux@roeck-us.net/ >>> >>> I'm not sure what happened to that series, but it looks like everybody >>> was mostly happy with it? >>> >> >> Major subsystem maintainers did not provide any feedback at all, and then >> there came the "it is not perfect enough" feedback, so I gave up on it. > > Well, if that means anything, we're interested even in something > imperfect if it solves the above case :) > Maybe someone else is interested picking it up (and no need for credits). I am buried in work and don't have the time (nor, frankly, much interest) to revive it. Also, just for reference: The patch series touches a total of 8 architectures, and unless I missed some I only got feedback from two architecture maintainers. That doesn't include arm - I don't recall if it doesn't need changes or if I never got there. Guenter ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-24 15:09 ` Guenter Roeck @ 2024-09-24 15:56 ` Jani Nikula 2024-09-24 16:35 ` Guenter Roeck 2024-09-24 16:57 ` Maxime Ripard 2024-09-25 11:52 ` Simona Vetter 1 sibling, 2 replies; 24+ messages in thread From: Jani Nikula @ 2024-09-24 15:56 UTC (permalink / raw) To: Guenter Roeck, Maxime Ripard Cc: Simona Vetter, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On Tue, 24 Sep 2024, Guenter Roeck <linux@roeck-us.net> wrote: >>>> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: >>>>> Yeah I think long-term we might want a kunit framework so that we can >>>>> catch dmesg warnings we expect and test for those, without those warnings >>>>> actually going to dmesg. Similar to how the lockdep tests also reroute >>>>> locking validation, so that the expected positive tests don't wreak >>>>> lockdep for real. >>>>> >>>>> But until that exists, we can't have tests that splat in dmesg when they >>>>> work as intended. > > FWIW, that is arguable. More and more tests are added which do add such splats, > and I don't see any hesitance by developers to adding more. So far I counted > two alone in this commit window, and that does not include new splats from > tests which I had already disabled. I simply disable those tests or don't > enable them in the first place if they are new. I did the same with the drm > unit tests due to the splats generated by the scaling unit tests, so any > additional drm unit test splats don't make a difference for me since the > tests are already disabled. What's the point of having unit tests that CI systems routinely have to filter out of test runs? Or filter warnings generated by the tests, potentially missing new warnings. Who is going to run the tests if the existing CI systems choose to ignore them? Automation on a massive scale is key here, and making that harder is counter-productive. BR, Jani. -- Jani Nikula, Intel ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-24 15:56 ` Jani Nikula @ 2024-09-24 16:35 ` Guenter Roeck 2024-09-24 16:57 ` Maxime Ripard 1 sibling, 0 replies; 24+ messages in thread From: Guenter Roeck @ 2024-09-24 16:35 UTC (permalink / raw) To: Jani Nikula, Maxime Ripard Cc: Simona Vetter, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On 9/24/24 08:56, Jani Nikula wrote: > On Tue, 24 Sep 2024, Guenter Roeck <linux@roeck-us.net> wrote: >>>>> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: >>>>>> Yeah I think long-term we might want a kunit framework so that we can >>>>>> catch dmesg warnings we expect and test for those, without those warnings >>>>>> actually going to dmesg. Similar to how the lockdep tests also reroute >>>>>> locking validation, so that the expected positive tests don't wreak >>>>>> lockdep for real. >>>>>> >>>>>> But until that exists, we can't have tests that splat in dmesg when they >>>>>> work as intended. >> >> FWIW, that is arguable. More and more tests are added which do add such splats, >> and I don't see any hesitance by developers to adding more. So far I counted >> two alone in this commit window, and that does not include new splats from >> tests which I had already disabled. I simply disable those tests or don't >> enable them in the first place if they are new. I did the same with the drm >> unit tests due to the splats generated by the scaling unit tests, so any >> additional drm unit test splats don't make a difference for me since the >> tests are already disabled. > > What's the point of having unit tests that CI systems routinely have to > filter out of test runs? Or filter warnings generated by the tests, > potentially missing new warnings. Who is going to run the tests if the > existing CI systems choose to ignore them? > > Automation on a massive scale is key here, and making that harder is > counter-productive. > As I have said elsewhere, not being able to handle backtraces generated on purpose is a limitation of my testbed. Other testbeds with active (and paid) maintainers may not have that limitation. I deal with it by disabling affected tests. Others may deal with it by maintaining exception lists. Ultimately it is up to developers and testbed maintainers to decide the level of test coverage they are looking for or able to support. Thanks, Guenter ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-24 15:56 ` Jani Nikula 2024-09-24 16:35 ` Guenter Roeck @ 2024-09-24 16:57 ` Maxime Ripard 2024-09-24 17:37 ` Guenter Roeck 2024-09-25 9:41 ` Jani Nikula 1 sibling, 2 replies; 24+ messages in thread From: Maxime Ripard @ 2024-09-24 16:57 UTC (permalink / raw) To: Jani Nikula Cc: Guenter Roeck, Simona Vetter, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson [-- Attachment #1: Type: text/plain, Size: 1770 bytes --] On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote: > On Tue, 24 Sep 2024, Guenter Roeck <linux@roeck-us.net> wrote: > >>>> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: > >>>>> Yeah I think long-term we might want a kunit framework so that we can > >>>>> catch dmesg warnings we expect and test for those, without those warnings > >>>>> actually going to dmesg. Similar to how the lockdep tests also reroute > >>>>> locking validation, so that the expected positive tests don't wreak > >>>>> lockdep for real. > >>>>> > >>>>> But until that exists, we can't have tests that splat in dmesg when they > >>>>> work as intended. > > > > FWIW, that is arguable. More and more tests are added which do add such splats, > > and I don't see any hesitance by developers to adding more. So far I counted > > two alone in this commit window, and that does not include new splats from > > tests which I had already disabled. I simply disable those tests or don't > > enable them in the first place if they are new. I did the same with the drm > > unit tests due to the splats generated by the scaling unit tests, so any > > additional drm unit test splats don't make a difference for me since the > > tests are already disabled. > > What's the point of having unit tests that CI systems routinely have to > filter out of test runs? Or filter warnings generated by the tests, > potentially missing new warnings. Who is going to run the tests if the > existing CI systems choose to ignore them? If we turn this argument around, that means we can't write unit test for code that will create a warning. IMO, this creates a bad incentive, and saying that any capable CI system should reject them is certainly opiniated. Maxime [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 273 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-24 16:57 ` Maxime Ripard @ 2024-09-24 17:37 ` Guenter Roeck 2024-09-25 9:41 ` Jani Nikula 1 sibling, 0 replies; 24+ messages in thread From: Guenter Roeck @ 2024-09-24 17:37 UTC (permalink / raw) To: Maxime Ripard, Jani Nikula Cc: Simona Vetter, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On 9/24/24 09:57, Maxime Ripard wrote: > On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote: >> On Tue, 24 Sep 2024, Guenter Roeck <linux@roeck-us.net> wrote: >>>>>> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: >>>>>>> Yeah I think long-term we might want a kunit framework so that we can >>>>>>> catch dmesg warnings we expect and test for those, without those warnings >>>>>>> actually going to dmesg. Similar to how the lockdep tests also reroute >>>>>>> locking validation, so that the expected positive tests don't wreak >>>>>>> lockdep for real. >>>>>>> >>>>>>> But until that exists, we can't have tests that splat in dmesg when they >>>>>>> work as intended. >>> >>> FWIW, that is arguable. More and more tests are added which do add such splats, >>> and I don't see any hesitance by developers to adding more. So far I counted >>> two alone in this commit window, and that does not include new splats from >>> tests which I had already disabled. I simply disable those tests or don't >>> enable them in the first place if they are new. I did the same with the drm >>> unit tests due to the splats generated by the scaling unit tests, so any >>> additional drm unit test splats don't make a difference for me since the >>> tests are already disabled. >> >> What's the point of having unit tests that CI systems routinely have to >> filter out of test runs? Or filter warnings generated by the tests, >> potentially missing new warnings. Who is going to run the tests if the >> existing CI systems choose to ignore them? > > If we turn this argument around, that means we can't write unit test for > code that will create a warning. > > IMO, this creates a bad incentive, and saying that any capable CI system > should reject them is certainly opiniated. > Agreed. All I am saying is that _I_ am rejecting them, but it is up to each individual testbed (or, rather, testbed maintainer) to decide how to handle the situation. Guenter ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-24 16:57 ` Maxime Ripard 2024-09-24 17:37 ` Guenter Roeck @ 2024-09-25 9:41 ` Jani Nikula 2024-09-25 12:59 ` Maxime Ripard 1 sibling, 1 reply; 24+ messages in thread From: Jani Nikula @ 2024-09-25 9:41 UTC (permalink / raw) To: Maxime Ripard Cc: Guenter Roeck, Simona Vetter, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On Tue, 24 Sep 2024, Maxime Ripard <mripard@kernel.org> wrote: > On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote: >> On Tue, 24 Sep 2024, Guenter Roeck <linux@roeck-us.net> wrote: >> >>>> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: >> >>>>> Yeah I think long-term we might want a kunit framework so that we can >> >>>>> catch dmesg warnings we expect and test for those, without those warnings >> >>>>> actually going to dmesg. Similar to how the lockdep tests also reroute >> >>>>> locking validation, so that the expected positive tests don't wreak >> >>>>> lockdep for real. >> >>>>> >> >>>>> But until that exists, we can't have tests that splat in dmesg when they >> >>>>> work as intended. >> > >> > FWIW, that is arguable. More and more tests are added which do add such splats, >> > and I don't see any hesitance by developers to adding more. So far I counted >> > two alone in this commit window, and that does not include new splats from >> > tests which I had already disabled. I simply disable those tests or don't >> > enable them in the first place if they are new. I did the same with the drm >> > unit tests due to the splats generated by the scaling unit tests, so any >> > additional drm unit test splats don't make a difference for me since the >> > tests are already disabled. >> >> What's the point of having unit tests that CI systems routinely have to >> filter out of test runs? Or filter warnings generated by the tests, >> potentially missing new warnings. Who is going to run the tests if the >> existing CI systems choose to ignore them? > > If we turn this argument around, that means we can't write unit test for > code that will create a warning. The question really is, which warnings we get because of the functionality being tested, and which warnings are due to an unexpected and unrelated bug? Is it a pass or fail if the test triggers an unrelated warning? If the developer runs the tests, are they expected to look at dmesg and inspect every warning to decide? > IMO, this creates a bad incentive, and saying that any capable CI system > should reject them is certainly opiniated. All I'm saying it generates an extra burden for current real world CI systems that run tests on a massive scale and even have paid maintainers. It's not trivial to sort out expected and unexpected warnings, and keep the filters updated every time the warnings change. It's not without a cost. And the end result might just be that the unit tests won't get run at all. Or warnings just get completely ignored for kunit tests. I don't completely disagree with you either. It's just that we don't have that automation on the kernel side, and in the mean time, perhaps we should be really conservative about the warnings we create in tests? If we can't filter out the warnings kernel side, perhaps we could figure out a way to annotate the kunit tests that generate warnings on passing runs? BR, Jani. -- Jani Nikula, Intel ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-25 9:41 ` Jani Nikula @ 2024-09-25 12:59 ` Maxime Ripard 2024-09-25 15:57 ` Guenter Roeck 0 siblings, 1 reply; 24+ messages in thread From: Maxime Ripard @ 2024-09-25 12:59 UTC (permalink / raw) To: Jani Nikula Cc: Guenter Roeck, Simona Vetter, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson [-- Attachment #1: Type: text/plain, Size: 3595 bytes --] On Wed, Sep 25, 2024 at 12:41:40PM GMT, Jani Nikula wrote: > On Tue, 24 Sep 2024, Maxime Ripard <mripard@kernel.org> wrote: > > On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote: > >> On Tue, 24 Sep 2024, Guenter Roeck <linux@roeck-us.net> wrote: > >> >>>> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: > >> >>>>> Yeah I think long-term we might want a kunit framework so that we can > >> >>>>> catch dmesg warnings we expect and test for those, without those warnings > >> >>>>> actually going to dmesg. Similar to how the lockdep tests also reroute > >> >>>>> locking validation, so that the expected positive tests don't wreak > >> >>>>> lockdep for real. > >> >>>>> > >> >>>>> But until that exists, we can't have tests that splat in dmesg when they > >> >>>>> work as intended. > >> > > >> > FWIW, that is arguable. More and more tests are added which do add such splats, > >> > and I don't see any hesitance by developers to adding more. So far I counted > >> > two alone in this commit window, and that does not include new splats from > >> > tests which I had already disabled. I simply disable those tests or don't > >> > enable them in the first place if they are new. I did the same with the drm > >> > unit tests due to the splats generated by the scaling unit tests, so any > >> > additional drm unit test splats don't make a difference for me since the > >> > tests are already disabled. > >> > >> What's the point of having unit tests that CI systems routinely have to > >> filter out of test runs? Or filter warnings generated by the tests, > >> potentially missing new warnings. Who is going to run the tests if the > >> existing CI systems choose to ignore them? > > > > If we turn this argument around, that means we can't write unit test for > > code that will create a warning. > > The question really is, which warnings we get because of the > functionality being tested, and which warnings are due to an unexpected > and unrelated bug? Is it a pass or fail if the test triggers an > unrelated warning? > > If the developer runs the tests, are they expected to look at dmesg and > inspect every warning to decide? No, there's no such expectation. Yet Intel's CI chose to do so, and chose to treat any warning as a failure, despite the fact that kunit doesn't have the same policy. > > IMO, this creates a bad incentive, and saying that any capable CI system > > should reject them is certainly opiniated. > > All I'm saying it generates an extra burden for current real world CI > systems that run tests on a massive scale and even have paid > maintainers. It's not trivial to sort out expected and unexpected > warnings, and keep the filters updated every time the warnings > change. It's not without a cost. And the end result might just be that > the unit tests won't get run at all. Or warnings just get completely > ignored for kunit tests. I realise it must take a significant amount of resources, but it's also self inflicted. You could also stop looking for warnings when running kunit. > I don't completely disagree with you either. It's just that we don't > have that automation on the kernel side, and in the mean time, perhaps > we should be really conservative about the warnings we create in tests? > > If we can't filter out the warnings kernel side, perhaps we could figure > out a way to annotate the kunit tests that generate warnings on passing > runs? Yeah, I think that would be the best solution. That's what Guenther's series was about :/ Maxime [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 273 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-25 12:59 ` Maxime Ripard @ 2024-09-25 15:57 ` Guenter Roeck 0 siblings, 0 replies; 24+ messages in thread From: Guenter Roeck @ 2024-09-25 15:57 UTC (permalink / raw) To: Maxime Ripard, Jani Nikula Cc: Simona Vetter, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On 9/25/24 05:59, Maxime Ripard wrote: ... >> All I'm saying it generates an extra burden for current real world CI >> systems that run tests on a massive scale and even have paid >> maintainers. It's not trivial to sort out expected and unexpected >> warnings, and keep the filters updated every time the warnings >> change. It's not without a cost. And the end result might just be that >> the unit tests won't get run at all. Or warnings just get completely >> ignored for kunit tests. > > I realise it must take a significant amount of resources, but it's also > self inflicted. You could also stop looking for warnings when running > kunit. > FWIW, that doesn't work if kunit tests are built into the kernel and run when booting the system. It also doesn't work well if kunit tests trigger a WARN_ONCE() because that causes any real subsequent warning to be dropped. Also, ignoring warnings while running a kunit test means that _real_ unexpected warnings triggered by those tests will be ignored as well. Guenter ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-24 15:09 ` Guenter Roeck 2024-09-24 15:56 ` Jani Nikula @ 2024-09-25 11:52 ` Simona Vetter 2024-09-25 13:05 ` Maxime Ripard 1 sibling, 1 reply; 24+ messages in thread From: Simona Vetter @ 2024-09-25 11:52 UTC (permalink / raw) To: Guenter Roeck Cc: Maxime Ripard, Simona Vetter, Jani Nikula, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On Tue, Sep 24, 2024 at 08:09:38AM -0700, Guenter Roeck wrote: > On 9/24/24 06:56, Maxime Ripard wrote: > > On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote: > > > On 9/24/24 04:54, Maxime Ripard wrote: > > > > +Guenter > > > > > > > > On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: > > > > > On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote: > > > > > > The tests consistently trigger WARNs in drm_framebuffer code. I'm not > > > > > > sure what the point is with type of belts and suspenders tests. The > > > > > > warnings *are* the way to flag erroneous API usage. > > > > > > > > > > > > Warnings in turn trigger failures in CI. Filtering the warnings are > > > > > > error prone, and, crucially, would also filter actual errors in case the > > > > > > kunit tests are not run. > > > > > > > > > > > > I acknowledge there may be complex test cases where you'd end up > > > > > > triggering warnings somewhere deep, but these are not it. These are > > > > > > simple. > > > > > > > > > > > > Revert the tests, back to the drawing board. > > > > > > > > > > Yeah I think long-term we might want a kunit framework so that we can > > > > > catch dmesg warnings we expect and test for those, without those warnings > > > > > actually going to dmesg. Similar to how the lockdep tests also reroute > > > > > locking validation, so that the expected positive tests don't wreak > > > > > lockdep for real. > > > > > > > > > > But until that exists, we can't have tests that splat in dmesg when they > > > > > work as intended. > > > > > > FWIW, that is arguable. More and more tests are added which do add such splats, > and I don't see any hesitance by developers to adding more. So far I counted > two alone in this commit window, and that does not include new splats from > tests which I had already disabled. I simply disable those tests or don't > enable them in the first place if they are new. I did the same with the drm > unit tests due to the splats generated by the scaling unit tests, so any > additional drm unit test splats don't make a difference for me since the > tests are already disabled. I think for at least drm the consensus is clear, we won't have kunit tests that splat. Personally I really don't see the point of unit tests that are somewhere between unecessarily hard or outright too much pain to deploy in a test rig: Either you don't run them (not great), or you filter splats and might filter too much (not great either) or you filter as little as possible and fight false positives (also kinda suboptimal). Especially for unit tests this stuff must be totally rock solid. We've had similar discussions in the past around unit tests that wasted too much cpu time with randomized combinatorial testing, and we've thrown those out too from drm. Test hygiene matters. Also this means if you see this stuff in drm unit tests (or related things like dma-buf/fence), please report or send revert. > > > > It should be pretty soon: > > > > https://lore.kernel.org/dri-devel/20240403131936.787234-1-linux@roeck-us.net/ > > > > > > > > I'm not sure what happened to that series, but it looks like everybody > > > > was mostly happy with it? > > > > > > > > > > Major subsystem maintainers did not provide any feedback at all, and then > > > there came the "it is not perfect enough" feedback, so I gave up on it. > > > > Well, if that means anything, we're interested even in something > > imperfect if it solves the above case :) > > > > Maybe someone else is interested picking it up (and no need for credits). > I am buried in work and don't have the time (nor, frankly, much interest) > to revive it. Also, just for reference: The patch series touches a total > of 8 architectures, and unless I missed some I only got feedback from two > architecture maintainers. That doesn't include arm - I don't recall if it > doesn't need changes or if I never got there. This is great, somehow I missed it and much appreciated for the initial version even if you can't push it further. Hopefully one of the folks working on drm kunit tests will pick it up, it will be needed here. Cheers, Sima -- Simona Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-25 11:52 ` Simona Vetter @ 2024-09-25 13:05 ` Maxime Ripard 2024-09-25 16:04 ` Guenter Roeck 2024-10-02 12:10 ` Jani Nikula 0 siblings, 2 replies; 24+ messages in thread From: Maxime Ripard @ 2024-09-25 13:05 UTC (permalink / raw) To: Simona Vetter Cc: Guenter Roeck, Jani Nikula, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson [-- Attachment #1: Type: text/plain, Size: 3487 bytes --] On Wed, Sep 25, 2024 at 01:52:02PM GMT, Simona Vetter wrote: > On Tue, Sep 24, 2024 at 08:09:38AM -0700, Guenter Roeck wrote: > > On 9/24/24 06:56, Maxime Ripard wrote: > > > On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote: > > > > On 9/24/24 04:54, Maxime Ripard wrote: > > > > > +Guenter > > > > > > > > > > On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote: > > > > > > On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote: > > > > > > > The tests consistently trigger WARNs in drm_framebuffer code. I'm not > > > > > > > sure what the point is with type of belts and suspenders tests. The > > > > > > > warnings *are* the way to flag erroneous API usage. > > > > > > > > > > > > > > Warnings in turn trigger failures in CI. Filtering the warnings are > > > > > > > error prone, and, crucially, would also filter actual errors in case the > > > > > > > kunit tests are not run. > > > > > > > > > > > > > > I acknowledge there may be complex test cases where you'd end up > > > > > > > triggering warnings somewhere deep, but these are not it. These are > > > > > > > simple. > > > > > > > > > > > > > > Revert the tests, back to the drawing board. > > > > > > > > > > > > Yeah I think long-term we might want a kunit framework so that we can > > > > > > catch dmesg warnings we expect and test for those, without those warnings > > > > > > actually going to dmesg. Similar to how the lockdep tests also reroute > > > > > > locking validation, so that the expected positive tests don't wreak > > > > > > lockdep for real. > > > > > > > > > > > > But until that exists, we can't have tests that splat in dmesg when they > > > > > > work as intended. > > > > > > > > > FWIW, that is arguable. More and more tests are added which do add such splats, > > and I don't see any hesitance by developers to adding more. So far I counted > > two alone in this commit window, and that does not include new splats from > > tests which I had already disabled. I simply disable those tests or don't > > enable them in the first place if they are new. I did the same with the drm > > unit tests due to the splats generated by the scaling unit tests, so any > > additional drm unit test splats don't make a difference for me since the > > tests are already disabled. > > I think for at least drm the consensus is clear, we won't have kunit tests > that splat. Where was that ever discussed? > Personally I really don't see the point of unit tests that are > somewhere between unecessarily hard or outright too much pain to > deploy in a test rig: Either you don't run them (not great), or you > filter splats and might filter too much (not great either) or you > filter as little as possible and fight false positives (also kinda > suboptimal). Or you don't do any of that, and just rely on the canonical way to run kunit test and trust it's going to pass tests that do indeed pass, and fail / warn on those that don't. > Especially for unit tests this stuff must be totally rock solid. Is there any evidence that those tests were not rock solid? > We've had similar discussions in the past around unit tests that wasted > too much cpu time with randomized combinatorial testing, and we've thrown > those out too from drm. Test hygiene matters. We had that discussion because those tests could run for up to around a minute on certain platforms. It's not the same issue at all? Maxime [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 273 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-25 13:05 ` Maxime Ripard @ 2024-09-25 16:04 ` Guenter Roeck 2024-09-26 7:05 ` Maxime Ripard 2024-10-02 12:10 ` Jani Nikula 1 sibling, 1 reply; 24+ messages in thread From: Guenter Roeck @ 2024-09-25 16:04 UTC (permalink / raw) To: Maxime Ripard, Simona Vetter Cc: Jani Nikula, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On 9/25/24 06:05, Maxime Ripard wrote: [ ... ] >> We've had similar discussions in the past around unit tests that wasted >> too much cpu time with randomized combinatorial testing, and we've thrown >> those out too from drm. Test hygiene matters. > > We had that discussion because those tests could run for up to around a > minute on certain platforms. It's not the same issue at all? > I added "kunit.stats_enabled=2 kunit.filter=speed>slow" to the kernel command line in my tests to avoid long-running tests. That works as long as slow tests are marked accordingly using KUNIT_CASE_SLOW(), KUNIT_SPEED_SLOW, or KUNIT_SPEED_VERY_SLOW. Guenter ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-25 16:04 ` Guenter Roeck @ 2024-09-26 7:05 ` Maxime Ripard 0 siblings, 0 replies; 24+ messages in thread From: Maxime Ripard @ 2024-09-26 7:05 UTC (permalink / raw) To: Guenter Roeck Cc: Simona Vetter, Jani Nikula, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson [-- Attachment #1: Type: text/plain, Size: 862 bytes --] On Wed, Sep 25, 2024 at 09:04:39AM GMT, Guenter Roeck wrote: > On 9/25/24 06:05, Maxime Ripard wrote: > [ ... ] > > > > We've had similar discussions in the past around unit tests that wasted > > > too much cpu time with randomized combinatorial testing, and we've thrown > > > those out too from drm. Test hygiene matters. > > > > We had that discussion because those tests could run for up to around a > > minute on certain platforms. It's not the same issue at all? > > > > I added "kunit.stats_enabled=2 kunit.filter=speed>slow" to the kernel command > line in my tests to avoid long-running tests. That works as long as slow tests > are marked accordingly using KUNIT_CASE_SLOW(), KUNIT_SPEED_SLOW, or > KUNIT_SPEED_VERY_SLOW. Yeah, and I've added a warning some time if a test runs for too long but isn't flagged as slow. Maxime [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 273 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-09-25 13:05 ` Maxime Ripard 2024-09-25 16:04 ` Guenter Roeck @ 2024-10-02 12:10 ` Jani Nikula 2024-10-03 12:04 ` Maxime Ripard 1 sibling, 1 reply; 24+ messages in thread From: Jani Nikula @ 2024-10-02 12:10 UTC (permalink / raw) To: Maxime Ripard, Simona Vetter Cc: Guenter Roeck, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson On Wed, 25 Sep 2024, Maxime Ripard <mripard@kernel.org> wrote: > On Wed, Sep 25, 2024 at 01:52:02PM GMT, Simona Vetter wrote: >> I think for at least drm the consensus is clear, we won't have kunit tests >> that splat. > > Where was that ever discussed? Well, where was it ever agreed that it's okay for drm kunit tests to emit warnings? :p >> Personally I really don't see the point of unit tests that are >> somewhere between unecessarily hard or outright too much pain to >> deploy in a test rig: Either you don't run them (not great), or you >> filter splats and might filter too much (not great either) or you >> filter as little as possible and fight false positives (also kinda >> suboptimal). > > Or you don't do any of that, and just rely on the canonical way to run > kunit test and trust it's going to pass tests that do indeed pass, and > fail / warn on those that don't. That still doesn't address code being tested emitting *unexpected* warnings. BR, Jani. -- Jani Nikula, Intel ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 0/2] drm: revert some framebuffer API tests 2024-10-02 12:10 ` Jani Nikula @ 2024-10-03 12:04 ` Maxime Ripard 0 siblings, 0 replies; 24+ messages in thread From: Maxime Ripard @ 2024-10-03 12:04 UTC (permalink / raw) To: Jani Nikula Cc: Simona Vetter, Guenter Roeck, dri-devel, intel-gfx, Carlos Eduardo Gallo Filho, Maarten Lankhorst, Thomas Zimmermann, Jeff Johnson [-- Attachment #1: Type: text/plain, Size: 1871 bytes --] On Wed, Oct 02, 2024 at 03:10:14PM GMT, Jani Nikula wrote: > On Wed, 25 Sep 2024, Maxime Ripard <mripard@kernel.org> wrote: > > On Wed, Sep 25, 2024 at 01:52:02PM GMT, Simona Vetter wrote: > >> I think for at least drm the consensus is clear, we won't have kunit tests > >> that splat. > > > > Where was that ever discussed? > > Well, where was it ever agreed that it's okay for drm kunit tests to > emit warnings? :p One policy is upstream, the other isn't. And it does seem like the consensus towards downstream patches and policies is pretty well established. And I wasn't the one claiming that there's a consensus to begin with, so I don't see why I should prove anything? > >> Personally I really don't see the point of unit tests that are > >> somewhere between unecessarily hard or outright too much pain to > >> deploy in a test rig: Either you don't run them (not great), or you > >> filter splats and might filter too much (not great either) or you > >> filter as little as possible and fight false positives (also kinda > >> suboptimal). > > > > Or you don't do any of that, and just rely on the canonical way to run > > kunit test and trust it's going to pass tests that do indeed pass, and > > fail / warn on those that don't. > > That still doesn't address code being tested emitting *unexpected* > warnings. Then make kunit report a warning / failure when there's an unexpected warning splat. At the end of the day, the discussion is that we already require for for each committer to: - Apply patches - Check for checkpatch issues - Solve potential conflicts - Make sure it compiles on three different architectures, with huge defconfigs - Make sure the unit tests still pass I'm not going to add "and grep through the output of those 1000-ish tests for a warning" to that list. Maxime [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 273 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2024-10-03 12:04 UTC | newest] Thread overview: 24+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2024-09-17 17:43 [PATCH 0/2] drm: revert some framebuffer API tests Jani Nikula 2024-09-17 17:43 ` [PATCH 1/2] Revert "drm/tests: Add test for drm_framebuffer_free()" Jani Nikula 2024-09-17 17:43 ` [PATCH 2/2] Revert "drm/tests: Add test for drm_framebuffer_init()" Jani Nikula 2024-09-17 19:01 ` ✗ Fi.CI.SPARSE: warning for drm: revert some framebuffer API tests Patchwork 2024-09-17 19:10 ` ✓ Fi.CI.BAT: success " Patchwork 2024-09-18 8:44 ` ✗ Fi.CI.IGT: failure " Patchwork 2024-09-24 10:06 ` [PATCH 0/2] " Simona Vetter 2024-09-24 11:54 ` Maxime Ripard 2024-09-24 13:37 ` Guenter Roeck 2024-09-24 13:56 ` Maxime Ripard 2024-09-24 15:09 ` Guenter Roeck 2024-09-24 15:56 ` Jani Nikula 2024-09-24 16:35 ` Guenter Roeck 2024-09-24 16:57 ` Maxime Ripard 2024-09-24 17:37 ` Guenter Roeck 2024-09-25 9:41 ` Jani Nikula 2024-09-25 12:59 ` Maxime Ripard 2024-09-25 15:57 ` Guenter Roeck 2024-09-25 11:52 ` Simona Vetter 2024-09-25 13:05 ` Maxime Ripard 2024-09-25 16:04 ` Guenter Roeck 2024-09-26 7:05 ` Maxime Ripard 2024-10-02 12:10 ` Jani Nikula 2024-10-03 12:04 ` Maxime Ripard
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).