Skip to contentSkip to conversation

Test cases for fbdev

PATCH In review Thomas Zimmermann 4 participants 16 messages Nov 20, 2020 – Nov 23, 2020

lore
Share & tools
lore
#0 lore raw

v6 cover Test cases for fbdev

This patchset adds read and write tests for fbdev. It compares the content of the framebuffer and reference buffer. A number of the special cases near the EOF are also tested.

Depending on the implementation (sys, cfb), fbdev read/write changes its semantics. Together with a kernel patches [1] these test cases intend to provide a reference.

v6:
* remove unaligned I/O from fast-feedback,testlist (Petri)
* actually use igt_assert() in nullptr test (Petri)
v5:
* test mmap() with igt_assert() (Daniel, Chris)
v4:
* declare variables as volatile where necessary (Petri)
* replace igt_require() with igt_assert() in several places (Petri)
* clarify several error messages (Petri)
* update CI
v3:
* put igt_describe() before the block it describes (Petri)
v2:
* move tests into subtest groups
* do setup in igt_fixtures (Daniel, Chris, Petri)
* add additional tests for unaligned access and NULL-pointer buffers (Daniel)

[1] https://patchwork.freedesktop.org/series/80038/

Thomas Zimmermann (8):
tests/fbdev: Move existing tests into separate subgroups tests/fbdev: Map framebuffer in igt_fixture tests/fbdev: Add tests for read operations on framebuffer tests/fbdev: Add tests for unaligned reads on framebuffer memory tests/fbdev: Add tests for write operations on framebuffer tests/fbdev: Add tests for unaligned writes on framebuffer memory tests/fbdev: Add tests for accessing framebuffer near EOF tests/fbdev: Add tests for read/writing with NULL-pointer buffers

 tests/fbdev.c                         | 223 ++++++++++++++++++++++++--
 tests/intel-ci/fast-feedback.testlist |   6 +-
 2 files changed, 212 insertions(+), 17 deletions(-)

--
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#1 lore raw

PATCH v6 1/8 tests/fbdev: Move existing tests into separate subgroups

Move the existing tests into subgroups for testing modesetting and accessing the framebuffer.

v5:
* test mmap() with igt_assert() (Daniel, Chris)
v4:
* declare fd as volatile (Petri)
* add info test to CI
v3:

	* put igt_describe() before igt_subtest() and igt_subtest_group()
	  (Petri)
---
 tests/fbdev.c                         | 53 ++++++++++++++++++++-------
 tests/intel-ci/fast-feedback.testlist |  1 +
 2 files changed, 41 insertions(+), 13 deletions(-)
tests/fbdev.c +40 -13
index e5efeb93..a803f445 100644
@@ -37,28 +37,17 @@
 
 #include "igt.h"
 
-igt_main
+static void mode_tests(int fd)
 {
 	struct fb_var_screeninfo var_info;
 	struct fb_fix_screeninfo fix_info;
-	int fd = -1;
 
-	/*
-	 * Should this test focus on the fbdev independent of any drm driver,
-	 * or should it look for fbdev of a particular device?
-	 */
 	igt_fixture {
-		fd = open("/dev/fb0", O_RDWR);
-		if (fd < 0) {
-			drm_load_module(DRIVER_ANY);
-			fd = open("/dev/fb0", O_RDWR);
-		}
-		igt_require_f(fd != -1, "/dev/fb0\n");
-
 		igt_require(ioctl(fd, FBIOGET_VSCREENINFO, &var_info) == 0);
 		igt_require(ioctl(fd, FBIOGET_FSCREENINFO, &fix_info) == 0);
 	}
 
+	igt_describe("Check if screeninfo is valid");
 	igt_subtest("info") {
 		unsigned long size;
 
@@ -69,7 +58,17 @@ igt_main
 			     fix_info.line_length,
 			     fix_info.smem_len);
 	}
+}
+
+static void framebuffer_tests(int fd)
+{
+	struct fb_fix_screeninfo fix_info;
+
+	igt_fixture {
+		igt_require(ioctl(fd, FBIOGET_FSCREENINFO, &fix_info) == 0);
+	}
 
+	igt_describe("Check mmap operations on framebuffer memory");
 	igt_subtest("mmap") {
 		void *map;
 
@@ -82,6 +81,34 @@ igt_main
 		memset(map, 0, fix_info.smem_len);
 		munmap(map, fix_info.smem_len);
 	}
+}
+
+igt_main
+{
+	volatile int fd = -1;
+
+	/*
+	 * Should this test focus on the fbdev independent of any drm driver,
+	 * or should it look for fbdev of a particular device?
+	 */
+	igt_fixture {
+		fd = open("/dev/fb0", O_RDWR);
+		if (fd < 0) {
+			drm_load_module(DRIVER_ANY);
+			fd = open("/dev/fb0", O_RDWR);
+		}
+		igt_require_f(fd != -1, "/dev/fb0\n");
+	}
+
+	igt_describe("Check modesetting");
+	igt_subtest_group {
+		mode_tests(fd);
+	}
+
+	igt_describe("Check framebuffer access");
+	igt_subtest_group {
+		framebuffer_tests(fd);
+	}
 
 	igt_fixture {
 		close(fd);
tests/intel-ci/fast-feedback.testlist +1 -0
index 83722f83..a40410a8 100644
@@ -2,6 +2,7 @@
 
 igt@core_auth@basic-auth
 igt@debugfs_test@read_all_entries
+igt@fbdev@info
 igt@fbdev@mmap
 igt@gem_basic@bad-close
 igt@gem_basic@create-close
Signature · 6 lines
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Reviewed-by on v6 1/8
#2 lore raw

Re: [igt-dev] [PATCH v6 1/8] tests/fbdev: Move existing tests into separate subgroups

Quoted 9 lines · Thomas Zimmermann

Move the existing tests into subgroups for testing modesetting and accessing the framebuffer.

v5:
* test mmap() with igt_assert() (Daniel, Chris)
v4:
* declare fd as volatile (Petri)
* add info test to CI
v3:

Quoted 4 lines
	* put igt_describe() before igt_subtest() and igt_subtest_group()
	  (Petri)
Quoted 108 lines
---
 tests/fbdev.c                         | 53 ++++++++++++++++++++-------
 tests/intel-ci/fast-feedback.testlist |  1 +
 2 files changed, 41 insertions(+), 13 deletions(-)
tests/fbdev.c +40 -13
index e5efeb93..a803f445 100644
@@ -37,28 +37,17 @@
 
 #include "igt.h"
 
-igt_main
+static void mode_tests(int fd)
 {
 	struct fb_var_screeninfo var_info;
 	struct fb_fix_screeninfo fix_info;
-	int fd = -1;
 
-	/*
-	 * Should this test focus on the fbdev independent of any drm driver,
-	 * or should it look for fbdev of a particular device?
-	 */
 	igt_fixture {
-		fd = open("/dev/fb0", O_RDWR);
-		if (fd < 0) {
-			drm_load_module(DRIVER_ANY);
-			fd = open("/dev/fb0", O_RDWR);
-		}
-		igt_require_f(fd != -1, "/dev/fb0\n");
-
 		igt_require(ioctl(fd, FBIOGET_VSCREENINFO, &var_info) == 0);
 		igt_require(ioctl(fd, FBIOGET_FSCREENINFO, &fix_info) == 0);
 	}
 
+	igt_describe("Check if screeninfo is valid");
 	igt_subtest("info") {
 		unsigned long size;
 
@@ -69,7 +58,17 @@ igt_main
 			     fix_info.line_length,
 			     fix_info.smem_len);
 	}
+}
+
+static void framebuffer_tests(int fd)
+{
+	struct fb_fix_screeninfo fix_info;
+
+	igt_fixture {
+		igt_require(ioctl(fd, FBIOGET_FSCREENINFO, &fix_info) == 0);
+	}
 
+	igt_describe("Check mmap operations on framebuffer memory");
 	igt_subtest("mmap") {
 		void *map;
 
@@ -82,6 +81,34 @@ igt_main
 		memset(map, 0, fix_info.smem_len);
 		munmap(map, fix_info.smem_len);
 	}
+}
+
+igt_main
+{
+	volatile int fd = -1;
+
+	/*
+	 * Should this test focus on the fbdev independent of any drm driver,
+	 * or should it look for fbdev of a particular device?
+	 */
+	igt_fixture {
+		fd = open("/dev/fb0", O_RDWR);
+		if (fd < 0) {
+			drm_load_module(DRIVER_ANY);
+			fd = open("/dev/fb0", O_RDWR);
+		}
+		igt_require_f(fd != -1, "/dev/fb0\n");
+	}
+
+	igt_describe("Check modesetting");
+	igt_subtest_group {
+		mode_tests(fd);
+	}
+
+	igt_describe("Check framebuffer access");
+	igt_subtest_group {
+		framebuffer_tests(fd);
+	}
 
 	igt_fixture {
 		close(fd);
tests/intel-ci/fast-feedback.testlist +1 -0
index 83722f83..a40410a8 100644
@@ -2,6 +2,7 @@
 
 igt@core_auth@basic-auth
 igt@debugfs_test@read_all_entries
+igt@fbdev@info
 igt@fbdev@mmap
 igt@gem_basic@bad-close
 igt@gem_basic@create-close
Signature · 1 line
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#3 lore raw

Re: [igt-dev] [PATCH v6 1/8] tests/fbdev: Move existing tests into separate subgroups

Am 23.11.20 um 12:27 schrieb Petri Latvala:

Quoted 13 lines · Thomas Zimmermann
Quoted 12 lines

Move the existing tests into subgroups for testing modesetting and accessing the framebuffer.

v5:
* test mmap() with igt_assert() (Daniel, Chris)
v4:
* declare fd as volatile (Petri)
* add info test to CI
v3:

	* put igt_describe() before igt_subtest() and igt_subtest_group()
	  (Petri)
Quoted 3 lines
Quoted 1 line

Thanks for your reviews.

Quoted 110 lines
Quoted 110 lines

---
  tests/fbdev.c                         | 53 ++++++++++++++++++++-------
  tests/intel-ci/fast-feedback.testlist |  1 +
  2 files changed, 41 insertions(+), 13 deletions(-)
tests/fbdev.c +40 -13
index e5efeb93..a803f445 100644
@@ -37,28 +37,17 @@
 
  #include "igt.h"
 
-igt_main
+static void mode_tests(int fd)
  {
  	struct fb_var_screeninfo var_info;
  	struct fb_fix_screeninfo fix_info;
-	int fd = -1;
 
-	/*
-	 * Should this test focus on the fbdev independent of any drm driver,
-	 * or should it look for fbdev of a particular device?
-	 */
  	igt_fixture {
-		fd = open("/dev/fb0", O_RDWR);
-		if (fd < 0) {
-			drm_load_module(DRIVER_ANY);
-			fd = open("/dev/fb0", O_RDWR);
-		}
-		igt_require_f(fd != -1, "/dev/fb0\n");
-
  		igt_require(ioctl(fd, FBIOGET_VSCREENINFO, &var_info) == 0);
  		igt_require(ioctl(fd, FBIOGET_FSCREENINFO, &fix_info) == 0);
  	}
 
+	igt_describe("Check if screeninfo is valid");
  	igt_subtest("info") {
  		unsigned long size;
 
@@ -69,7 +58,17 @@ igt_main
  			     fix_info.line_length,
  			     fix_info.smem_len);
  	}
+}
+
+static void framebuffer_tests(int fd)
+{
+	struct fb_fix_screeninfo fix_info;
+
+	igt_fixture {
+		igt_require(ioctl(fd, FBIOGET_FSCREENINFO, &fix_info) == 0);
+	}
 
+	igt_describe("Check mmap operations on framebuffer memory");
  	igt_subtest("mmap") {
  		void *map;
 
@@ -82,6 +81,34 @@ igt_main
  		memset(map, 0, fix_info.smem_len);
  		munmap(map, fix_info.smem_len);
  	}
+}
+
+igt_main
+{
+	volatile int fd = -1;
+
+	/*
+	 * Should this test focus on the fbdev independent of any drm driver,
+	 * or should it look for fbdev of a particular device?
+	 */
+	igt_fixture {
+		fd = open("/dev/fb0", O_RDWR);
+		if (fd < 0) {
+			drm_load_module(DRIVER_ANY);
+			fd = open("/dev/fb0", O_RDWR);
+		}
+		igt_require_f(fd != -1, "/dev/fb0\n");
+	}
+
+	igt_describe("Check modesetting");
+	igt_subtest_group {
+		mode_tests(fd);
+	}
+
+	igt_describe("Check framebuffer access");
+	igt_subtest_group {
+		framebuffer_tests(fd);
+	}
 
  	igt_fixture {
  		close(fd);
tests/intel-ci/fast-feedback.testlist +1 -0
index 83722f83..a40410a8 100644
@@ -2,6 +2,7 @@
 
  igt@core_auth@basic-auth
  igt@debugfs_test@read_all_entries
+igt@fbdev@info
  igt@fbdev@mmap
  igt@gem_basic@bad-close
  igt@gem_basic@create-close
Signature · 1 line
2.29.2
Signature · 6 lines
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#4 lore raw

PATCH v6 2/8 tests/fbdev: Map framebuffer in igt_fixture

In reply to Thomas Zimmermann

The mapping of the framebuffer memory will be useful for read/write tests. Move it into an igt_fixture block.

v4:
* declare map as volatile (Petri)
* test struct fb_fix_screeninfo.smem_len with igt_assert()
* remove mmap test from CI

---
 tests/fbdev.c                         | 12 +++++-------
 tests/intel-ci/fast-feedback.testlist |  1 -
 2 files changed, 5 insertions(+), 8 deletions(-)
tests/fbdev.c +5 -7
index a803f445..eebd2a83 100644
@@ -63,22 +63,20 @@ static void mode_tests(int fd)
 static void framebuffer_tests(int fd)
 {
 	struct fb_fix_screeninfo fix_info;
+	void * volatile map;
 
 	igt_fixture {
 		igt_require(ioctl(fd, FBIOGET_FSCREENINFO, &fix_info) == 0);
-	}
-
-	igt_describe("Check mmap operations on framebuffer memory");
-	igt_subtest("mmap") {
-		void *map;
-
-		igt_require(fix_info.smem_len);
+		igt_assert(fix_info.smem_len);
 
 		map = mmap(NULL, fix_info.smem_len,
 			   PROT_WRITE, MAP_SHARED, fd, 0);
 		igt_assert(map != MAP_FAILED);
 
 		memset(map, 0, fix_info.smem_len);
+	}
+
+	igt_fixture {
 		munmap(map, fix_info.smem_len);
 	}
 }
tests/intel-ci/fast-feedback.testlist +0 -1
index a40410a8..cf66b4da 100644
@@ -3,7 +3,6 @@
 igt@core_auth@basic-auth
 igt@debugfs_test@read_all_entries
 igt@fbdev@info
-igt@fbdev@mmap
 igt@gem_basic@bad-close
 igt@gem_basic@create-close
 igt@gem_basic@create-fd-close
Signature · 6 lines
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Reviewed-by on v6 2/8
#5 lore raw

Re: [igt-dev] [PATCH v6 2/8] tests/fbdev: Map framebuffer in igt_fixture

Quoted 9 lines · Thomas Zimmermann

The mapping of the framebuffer memory will be useful for read/write tests. Move it into an igt_fixture block.

v4:
* declare map as volatile (Petri)
* test struct fb_fix_screeninfo.smem_len with igt_assert()
* remove mmap test from CI

This commit is not as standalone as one would hope, but it's standalone enough to not break too much without the rest of the series...

Quoted 52 lines
---
 tests/fbdev.c                         | 12 +++++-------
 tests/intel-ci/fast-feedback.testlist |  1 -
 2 files changed, 5 insertions(+), 8 deletions(-)
tests/fbdev.c +5 -7
index a803f445..eebd2a83 100644
@@ -63,22 +63,20 @@ static void mode_tests(int fd)
 static void framebuffer_tests(int fd)
 {
 	struct fb_fix_screeninfo fix_info;
+	void * volatile map;
 
 	igt_fixture {
 		igt_require(ioctl(fd, FBIOGET_FSCREENINFO, &fix_info) == 0);
-	}
-
-	igt_describe("Check mmap operations on framebuffer memory");
-	igt_subtest("mmap") {
-		void *map;
-
-		igt_require(fix_info.smem_len);
+		igt_assert(fix_info.smem_len);
 
 		map = mmap(NULL, fix_info.smem_len,
 			   PROT_WRITE, MAP_SHARED, fd, 0);
 		igt_assert(map != MAP_FAILED);
 
 		memset(map, 0, fix_info.smem_len);
+	}
+
+	igt_fixture {
 		munmap(map, fix_info.smem_len);
 	}
 }
tests/intel-ci/fast-feedback.testlist +0 -1
index a40410a8..cf66b4da 100644
@@ -3,7 +3,6 @@
 igt@core_auth@basic-auth
 igt@debugfs_test@read_all_entries
 igt@fbdev@info
-igt@fbdev@mmap
 igt@gem_basic@bad-close
 igt@gem_basic@create-close
 igt@gem_basic@create-fd-close
Signature · 1 line
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#6 lore raw

PATCH v6 3/8 tests/fbdev: Add tests for read operations on framebuffer

In reply to Thomas Zimmermann

The read tests check the read buffer against the content of the mapped framebuffer.

v4:
* test malloc() success with igt_require()
* replace igt_require() by igt_assert() in "read" (Petri)
* add read test to CI
v3:
* put igt_describe() before igt_subtest() (Petri)

---
 tests/fbdev.c                         | 25 +++++++++++++++++++++++++
 tests/intel-ci/fast-feedback.testlist |  1 +
 2 files changed, 26 insertions(+)
tests/fbdev.c +25 -0
index eebd2a83..d8c78a5e 100644
@@ -25,6 +25,7 @@
 
 #include "igt.h"
 
+#include <errno.h>
 #include <fcntl.h>
 #include <string.h>
 #include <sys/ioctl.h>
@@ -64,6 +65,7 @@ static void framebuffer_tests(int fd)
 {
 	struct fb_fix_screeninfo fix_info;
 	void * volatile map;
+	void * volatile buf;
 
 	igt_fixture {
 		igt_require(ioctl(fd, FBIOGET_FSCREENINFO, &fix_info) == 0);
@@ -73,10 +75,33 @@ static void framebuffer_tests(int fd)
 			   PROT_WRITE, MAP_SHARED, fd, 0);
 		igt_assert(map != MAP_FAILED);
 
+		buf = malloc(fix_info.smem_len);
+		igt_require(buf);
+	}
+
+	igt_describe("Check read operations on framebuffer memory");
+	igt_subtest("read") {
+		ssize_t ret;
+		int cmp;
+
+		/* fill framebuffer with 0 and compare */
 		memset(map, 0, fix_info.smem_len);
+		ret = pread(fd, buf, fix_info.smem_len, 0);
+		igt_assert_f(ret == (ssize_t)fix_info.smem_len, "pread failed, ret=%zd\n", ret);
+		cmp = memcmp(map, buf, fix_info.smem_len);
+		igt_assert_f(!cmp, "read buffer differs from mapped framebuffer for 0\n");
+
+		/* fill framebuffer with 0x55 and compare */
+		memset(map, 0x55, fix_info.smem_len);
+		ret = pread(fd, buf, fix_info.smem_len, 0);
+		igt_assert_f(ret == (ssize_t)fix_info.smem_len, "pread failed, ret=%zd\n", ret);
+		cmp = memcmp(map, buf, fix_info.smem_len);
+		igt_assert_f(!cmp, "read buffer differs from mapped framebuffer for 0x55\n");
 	}
 
 	igt_fixture {
+		free(buf);
+		memset(map, 0, fix_info.smem_len); // don't leave garbage on the screen
 		munmap(map, fix_info.smem_len);
 	}
 }
tests/intel-ci/fast-feedback.testlist +1 -0
index cf66b4da..fc8a605f 100644
@@ -3,6 +3,7 @@
 igt@core_auth@basic-auth
 igt@debugfs_test@read_all_entries
 igt@fbdev@info
+igt@fbdev@read
 igt@gem_basic@bad-close
 igt@gem_basic@create-close
 igt@gem_basic@create-fd-close
Signature · 6 lines
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
#7 lore raw

PATCH v6 4/8 tests/fbdev: Add tests for unaligned reads on framebuffer memory

In reply to Thomas Zimmermann

The tests for unaligned reads start and stop reading within pages.

v6:
* remove test from fast-feedback.testlist
v4:
* declare pagesize as volatile
* test sysconf() success with igt_require() (Petri)
* clarify error message about frambuffer size (Petri)
* replace igt_require() by igt_assert() in "unaligned-read" (Petri)
* add unaligned-read test to CI
v3:
* put igt_describe() before igt_subtest() (Petri)

---
 tests/fbdev.c | 40 ++++++++++++++++++++++++++++++++++++++--
 1 file changed, 38 insertions(+), 2 deletions(-)
tests/fbdev.c +38 -2
index d8c78a5e..be9e95c1 100644
@@ -64,10 +64,13 @@ static void mode_tests(int fd)
 static void framebuffer_tests(int fd)
 {
 	struct fb_fix_screeninfo fix_info;
-	void * volatile map;
-	void * volatile buf;
+	unsigned char * volatile map;
+	unsigned char * volatile buf;
+	volatile size_t pagesize;
 
 	igt_fixture {
+		long ret;
+
 		igt_require(ioctl(fd, FBIOGET_FSCREENINFO, &fix_info) == 0);
 		igt_assert(fix_info.smem_len);
 
@@ -77,6 +80,10 @@ static void framebuffer_tests(int fd)
 
 		buf = malloc(fix_info.smem_len);
 		igt_require(buf);
+
+		ret = sysconf(_SC_PAGESIZE);
+		igt_require(ret != -1);
+		pagesize = ret;
 	}
 
 	igt_describe("Check read operations on framebuffer memory");
@@ -99,6 +106,35 @@ static void framebuffer_tests(int fd)
 		igt_assert_f(!cmp, "read buffer differs from mapped framebuffer for 0x55\n");
 	}
 
+	igt_describe("Check read operations on unaligned locations in framebuffer memory");
+	igt_subtest("unaligned-read") {
+		off_t off;
+		size_t len;
+		ssize_t ret;
+		const unsigned char *pos;
+
+		off = pagesize + (pagesize >> 2); // 1.25 * pagesize
+		len = (pagesize << 2) + (pagesize >> 1); // 4.5 * pagesize
+		igt_require_f((off + len) < fix_info.smem_len, "framebuffer too small to test\n");
+
+		/* read at unaligned location and compare */
+		memset(map, 0, fix_info.smem_len);
+		memset(&map[off], 0x55, len);
+		memset(buf, 0xff, fix_info.smem_len);
+		ret = pread(fd, &buf[off], len, off);
+		igt_assert_f(ret == (ssize_t)len, "pread failed, ret=%zd\n", ret);
+		pos = memchr(buf, 0x55, fix_info.smem_len);
+		igt_assert_f(pos, "0x55 not found within read buffer\n");
+		igt_assert_f(pos == &buf[off], "0x55 found at pos %zu, expected %lld\n",
+			     pos - buf, (long long)off);
+		pos = memchr(&buf[off], 0xff, fix_info.smem_len - off);
+		igt_assert_f(pos, "0xff not found within read buffer\n");
+		igt_assert_f(pos == &buf[off + len], "0xff found at pos %zu, expected %lld\n",
+			     pos - buf, (long long)(off + len));
+		pos = memchr(&buf[off + len], 0x55, fix_info.smem_len - off + len);
+		igt_assert_f(pos, "found 0x55 at pos %zu, none expected\n", pos - buf);
+	}
+
 	igt_fixture {
 		free(buf);
 		memset(map, 0, fix_info.smem_len); // don't leave garbage on the screen
Signature · 6 lines
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
#8 lore raw

PATCH v6 5/8 tests/fbdev: Add tests for write operations on framebuffer

In reply to Thomas Zimmermann

The write tests check the written buffer against the content of the mapped framebuffer.

v4:
* replace igt_require() by iqt_assert() in "write" (Petri)
* add write test to CI
v3:
* put igt_describe() before igt_subtest() (Petri)

---
 tests/fbdev.c                         | 20 ++++++++++++++++++++
 tests/intel-ci/fast-feedback.testlist |  1 +
 2 files changed, 21 insertions(+)
tests/fbdev.c +20 -0
index be9e95c1..23ff146c 100644
@@ -135,6 +135,26 @@ static void framebuffer_tests(int fd)
 		igt_assert_f(pos, "found 0x55 at pos %zu, none expected\n", pos - buf);
 	}
 
+	igt_describe("Check write operations on framebuffer memory");
+	igt_subtest("write") {
+		ssize_t ret;
+		int cmp;
+
+		/* write 0 to framebuffer and compare */
+		memset(buf, 0, fix_info.smem_len);
+		ret = pwrite(fd, buf, fix_info.smem_len, 0);
+		igt_assert_f(ret == (ssize_t)fix_info.smem_len, "pwrite failed, ret=%zd\n", ret);
+		cmp = memcmp(map, buf, fix_info.smem_len);
+		igt_assert_f(!cmp, "write buffer differs from mapped framebuffer for 0\n");
+
+		/* write 0x55 to framebuffer and compare */
+		memset(buf, 0x55, fix_info.smem_len);
+		ret = pwrite(fd, buf, fix_info.smem_len, 0);
+		igt_assert_f(ret == (ssize_t)fix_info.smem_len, "pwrite failed, ret=%zd\n", ret);
+		cmp = memcmp(map, buf, fix_info.smem_len);
+		igt_assert_f(!cmp, "write buffer differs from mapped framebuffer for 0\n");
+	}
+
 	igt_fixture {
 		free(buf);
 		memset(map, 0, fix_info.smem_len); // don't leave garbage on the screen
tests/intel-ci/fast-feedback.testlist +1 -0
index fc8a605f..58e2ac1c 100644
@@ -4,6 +4,7 @@ igt@core_auth@basic-auth
 igt@debugfs_test@read_all_entries
 igt@fbdev@info
 igt@fbdev@read
+igt@fbdev@write
 igt@gem_basic@bad-close
 igt@gem_basic@create-close
 igt@gem_basic@create-fd-close
Signature · 6 lines
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
#9 lore raw

PATCH v6 6/8 tests/fbdev: Add tests for unaligned writes on framebuffer memory

In reply to Thomas Zimmermann

The tests for unaligned writes start and stop writing within pages.

v6:
* remove test from fast-feedback.testlist
v4:
* replace igt_require() by igt_assert() in "unaligned-write" (Petri)
* clarify error message about framebuffer size (Petri)
* add unaligned-write test to CI
v3:
* put igt_describe() before igt_subtest() (Petri)

---
 tests/fbdev.c | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
tests/fbdev.c +29 -0
index 23ff146c..c4cb357f 100644
@@ -155,6 +155,35 @@ static void framebuffer_tests(int fd)
 		igt_assert_f(!cmp, "write buffer differs from mapped framebuffer for 0\n");
 	}
 
+	igt_describe("Check write operations on unaligned locations in framebuffer memory");
+	igt_subtest("unaligned-write") {
+		off_t off;
+		size_t len;
+		ssize_t ret;
+		const unsigned char *pos;
+
+		off = pagesize + (pagesize >> 2); // 1.25 * pagesize
+		len = (pagesize << 2) + (pagesize >> 1); // 4.5 * pagesize
+		igt_require_f((off + len) < fix_info.smem_len, "framebuffer too small to test\n");
+
+		/* read at unaligned location and compare */
+		memset(map, 0xff, fix_info.smem_len);
+		memset(buf, 0, fix_info.smem_len);
+		memset(&buf[off], 0x55, len);
+		ret = pwrite(fd, &buf[off], len, off);
+		igt_assert_f(ret == (ssize_t)len, "pwrite failed, ret=%zd\n", ret);
+		pos = memchr(map, 0x55, fix_info.smem_len);
+		igt_assert_f(pos, "0x55 not found within framebuffer\n");
+		igt_assert_f(pos == &map[off], "0x55 found at pos %zu, expected %lld\n",
+			     pos - map, (long long)off);
+		pos = memchr(&map[off], 0xff, fix_info.smem_len - off);
+		igt_assert_f(pos, "0xff not found within framebuffer\n");
+		igt_assert_f(pos == &map[off + len], "0xff found at pos %zu, expected %lld\n",
+			     pos - map, (long long)(off + len));
+		pos = memchr(&map[off + len], 0x55, fix_info.smem_len - off + len);
+		igt_assert_f(pos, "found 0x55 at pos %zu, none expected\n", pos - map);
+	}
+
 	igt_fixture {
 		free(buf);
 		memset(map, 0, fix_info.smem_len); // don't leave garbage on the screen
Signature · 6 lines
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Reviewed-by on v6 6/8
#10 lore raw

Re: [igt-dev] [PATCH v6 6/8] tests/fbdev: Add tests for unaligned writes on framebuffer memory

Quoting Thomas Zimmermann (2020-11-20 10:52:15)

Quoted 41 lines

The tests for unaligned writes start and stop writing within pages.

v6:
* remove test from fast-feedback.testlist
v4:
* replace igt_require() by igt_assert() in "unaligned-write" (Petri)
* clarify error message about framebuffer size (Petri)
* add unaligned-write test to CI
v3:
* put igt_describe() before igt_subtest() (Petri)

---
 tests/fbdev.c | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
tests/fbdev.c +17 -0
index 23ff146c..c4cb357f 100644
@@ -155,6 +155,35 @@ static void framebuffer_tests(int fd)
                igt_assert_f(!cmp, "write buffer differs from mapped framebuffer for 0\n");
        }
 
+       igt_describe("Check write operations on unaligned locations in framebuffer memory");
+       igt_subtest("unaligned-write") {
+               off_t off;
+               size_t len;
+               ssize_t ret;
+               const unsigned char *pos;
+
+               off = pagesize + (pagesize >> 2); // 1.25 * pagesize
+               len = (pagesize << 2) + (pagesize >> 1); // 4.5 * pagesize
+               igt_require_f((off + len) < fix_info.smem_len, "framebuffer too small to test\n");
+
+               /* read at unaligned location and compare */
+               memset(map, 0xff, fix_info.smem_len);
+               memset(buf, 0, fix_info.smem_len);
+               memset(&buf[off], 0x55, len);
+               ret = pwrite(fd, &buf[off], len, off);
+               igt_assert_f(ret == (ssize_t)len, "pwrite failed, ret=%zd\n", ret);

tests/fbdev.c static void framebuffer_tests(int fd) · line 184

Quoted 10 lines
tests/fbdev.c +9 -0
+               pos = memchr(map, 0x55, fix_info.smem_len);
+               igt_assert_f(pos, "0x55 not found within framebuffer\n");
+               igt_assert_f(pos == &map[off], "0x55 found at pos %zu, expected %lld\n",
+                            pos - map, (long long)off);
+               pos = memchr(&map[off], 0xff, fix_info.smem_len - off);
+               igt_assert_f(pos, "0xff not found within framebuffer\n");
+               igt_assert_f(pos == &map[off + len], "0xff found at pos %zu, expected %lld\n",
+                            pos - map, (long long)(off + len));
 
+               pos = memchr(&map[off + len], 0x55, fix_info.smem_len - off + len);

Spotted this typo in the unaligned read/write, should be
smem_len - (off + len)

Applied some minor whitespace changes, the goal is to follow the kernel coding style (so that we don't have to keep on switching styles :), and that also allows us to use the same gcc-isms as we expect to find in the kernel.

Series is

and pushed.
-Chris
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#11 lore raw

Re: [igt-dev] [PATCH v6 6/8] tests/fbdev: Add tests for unaligned writes on framebuffer memory

Hi

Am 23.11.20 um 14:18 schrieb Chris Wilson:

Quoted 56 lines

Quoting Thomas Zimmermann (2020-11-20 10:52:15)

Quoted 41 lines

The tests for unaligned writes start and stop writing within pages.

v6:
* remove test from fast-feedback.testlist
v4:
* replace igt_require() by igt_assert() in "unaligned-write" (Petri)
* clarify error message about framebuffer size (Petri)
* add unaligned-write test to CI
v3:
* put igt_describe() before igt_subtest() (Petri)

---
  tests/fbdev.c | 29 +++++++++++++++++++++++++++++
  1 file changed, 29 insertions(+)
tests/fbdev.c +17 -0
index 23ff146c..c4cb357f 100644
@@ -155,6 +155,35 @@ static void framebuffer_tests(int fd)
                 igt_assert_f(!cmp, "write buffer differs from mapped framebuffer for 0\n");
         }
 
+       igt_describe("Check write operations on unaligned locations in framebuffer memory");
+       igt_subtest("unaligned-write") {
+               off_t off;
+               size_t len;
+               ssize_t ret;
+               const unsigned char *pos;
+
+               off = pagesize + (pagesize >> 2); // 1.25 * pagesize
+               len = (pagesize << 2) + (pagesize >> 1); // 4.5 * pagesize
+               igt_require_f((off + len) < fix_info.smem_len, "framebuffer too small to test\n");
+
+               /* read at unaligned location and compare */
+               memset(map, 0xff, fix_info.smem_len);
+               memset(buf, 0, fix_info.smem_len);
+               memset(&buf[off], 0x55, len);
+               ret = pwrite(fd, &buf[off], len, off);
+               igt_assert_f(ret == (ssize_t)len, "pwrite failed, ret=%zd\n", ret);

tests/fbdev.c static void framebuffer_tests(int fd) · line 184

Quoted 10 lines
tests/fbdev.c +9 -0
+               pos = memchr(map, 0x55, fix_info.smem_len);
+               igt_assert_f(pos, "0x55 not found within framebuffer\n");
+               igt_assert_f(pos == &map[off], "0x55 found at pos %zu, expected %lld\n",
+                            pos - map, (long long)off);
+               pos = memchr(&map[off], 0xff, fix_info.smem_len - off);
+               igt_assert_f(pos, "0xff not found within framebuffer\n");
+               igt_assert_f(pos == &map[off + len], "0xff found at pos %zu, expected %lld\n",
+                            pos - map, (long long)(off + len));
 
+               pos = memchr(&map[off + len], 0x55, fix_info.smem_len - off + len);

Spotted this typo in the unaligned read/write, should be
smem_len - (off + len)

Quoted 8 lines

Applied some minor whitespace changes, the goal is to follow the kernel coding style (so that we don't have to keep on switching styles :), and that also allows us to use the same gcc-isms as we expect to find in the kernel.

Series is

and pushed.

Thanks a lot!

Quoted 2 lines

-Chris

Signature · 6 lines
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#12 lore raw

PATCH v6 7/8 tests/fbdev: Add tests for accessing framebuffer near EOF

In reply to Thomas Zimmermann

Fbdev has some specific behavior when reading/writing near the EOF, which the eof test checks. If at least one bytes has been written, the number of bytes has to be returned, otherwise an error code (if any) has to be returned, or otherwise 0 has to returned. Not all drivers get this right.

v4:
* replace igt_require() by igt_assert() in "eof" (Petri)
* add eof test to CI
v3:
* put igt_describe() before igt_subtest() (Petri)

---
 tests/fbdev.c                         | 47 ++++++++++++++++++++++++++-
 tests/intel-ci/fast-feedback.testlist |  1 +
 2 files changed, 47 insertions(+), 1 deletion(-)
tests/fbdev.c +46 -1
index c4cb357f..62aa99b4 100644
@@ -78,7 +78,8 @@ static void framebuffer_tests(int fd)
 			   PROT_WRITE, MAP_SHARED, fd, 0);
 		igt_assert(map != MAP_FAILED);
 
-		buf = malloc(fix_info.smem_len);
+		/* allocate two additional bytes for eof test */
+		buf = malloc(fix_info.smem_len + 2);
 		igt_require(buf);
 
 		ret = sysconf(_SC_PAGESIZE);
@@ -184,6 +185,50 @@ static void framebuffer_tests(int fd)
 		igt_assert_f(pos, "found 0x55 at pos %zu, none expected\n", pos - map);
 	}
 
+	igt_describe("Check framebuffer access near EOF");
+	igt_subtest("eof") {
+		unsigned long lastindex = fix_info.smem_len - 1;
+		unsigned char *maplast = &((unsigned char *)map)[lastindex];
+		unsigned char *buflast = &((unsigned char *)buf)[lastindex];
+		ssize_t ret;
+
+		*buflast = 0x55;
+
+		/* write across EOF; set remaining bytes */
+		ret = pwrite(fd, buflast, 2, lastindex);
+		igt_assert_f(ret == 1, "write crossed EOF, ret=%zd\n", ret);
+		igt_assert_f(*maplast == *buflast, "write buffer differs from mapped framebuffer at final byte, "
+						   "maplast=%u buflast=%u\n", *maplast, *buflast);
+
+		/* write at EOF; get ENOSPC */
+		ret = pwrite(fd, &buflast[1], 1, lastindex + 1);
+		igt_assert_f((ret == -1) && (errno == ENOSPC), "write at EOF, ret=%zd\n", ret);
+
+		*maplast = 0;
+
+		/* write final byte */
+		ret = pwrite(fd, buflast, 1, lastindex);
+		igt_assert_f(ret == 1, "write before EOF, ret=%zd\n", ret);
+		igt_assert_f(*maplast == *buflast, "write buffer differs from mapped framebuffer at final byte, "
+						   "maplast=%u buflast=%u\n", *maplast, *buflast);
+
+		/* write after EOF; get EFBIG */
+		ret = pwrite(fd, &buflast[2], 1, lastindex + 2);
+		igt_assert_f((ret == -1) && (errno == EFBIG), "write after EOF, ret=%zd\n", ret);
+
+		*maplast = 0;
+
+		/* read across the EOF; get remaining bytes */
+		ret = pread(fd, buflast, 2, lastindex);
+		igt_assert_f(ret == 1, "read before EOF, ret=%zd\n", ret);
+		igt_assert_f(*maplast == *buflast, "read buffer differs from mapped framebuffer at final byte, "
+						   "maplast=%u buflast=%u\n", *maplast, *buflast);
+
+		/* read after EOF; get 0 */
+		ret = pread(fd, &buflast[1], 1, lastindex + 1);
+		igt_assert_f(ret == 0, "read at EOF, ret=%zd\n", ret);
+	}
+
 	igt_fixture {
 		free(buf);
 		memset(map, 0, fix_info.smem_len); // don't leave garbage on the screen
tests/intel-ci/fast-feedback.testlist +1 -0
index 58e2ac1c..9e0b71e9 100644
@@ -2,6 +2,7 @@
 
 igt@core_auth@basic-auth
 igt@debugfs_test@read_all_entries
+igt@fbdev@eof
 igt@fbdev@info
 igt@fbdev@read
 igt@fbdev@write
Signature · 6 lines
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
#13 lore raw

PATCH v6 8/8 tests/fbdev: Add tests for read/writing with NULL-pointer buffers

In reply to Thomas Zimmermann

Trying to read and write with a NULL-pointer buffer should fail and report EFAULT.

v6:
* actually replace igt_require() (Petri)
v4:
* replace igt_require() by igt_assert() in "nullptr" (Petri)
* add nullptr test to CI
v3:
* put igt_describe() before igt_subtest() (Petri)

---
 tests/fbdev.c                         | 11 +++++++++++
 tests/intel-ci/fast-feedback.testlist |  1 +
 2 files changed, 12 insertions(+)
tests/fbdev.c +11 -0
index 62aa99b4..598e2963 100644
@@ -229,6 +229,17 @@ static void framebuffer_tests(int fd)
 		igt_assert_f(ret == 0, "read at EOF, ret=%zd\n", ret);
 	}
 
+	igt_describe("Check framebuffer access with NULL");
+	igt_subtest("nullptr") {
+		ssize_t ret;
+
+		ret = pread(fd, NULL, fix_info.smem_len, 0);
+		igt_assert_f((ret == -1) && (errno == EFAULT), "reading into NULL did not return EFAULT, ret=%zd\n", ret);
+
+		ret = pwrite(fd, NULL, fix_info.smem_len, 0);
+		igt_assert_f((ret == -1) && (errno == EFAULT), "writing from NULL did not return EFAULT, ret=%zd\n", ret);
+	}
+
 	igt_fixture {
 		free(buf);
 		memset(map, 0, fix_info.smem_len); // don't leave garbage on the screen
tests/intel-ci/fast-feedback.testlist +1 -0
index 9e0b71e9..eaa904fa 100644
@@ -4,6 +4,7 @@ igt@core_auth@basic-auth
 igt@debugfs_test@read_all_entries
 igt@fbdev@eof
 igt@fbdev@info
+igt@fbdev@nullptr
 igt@fbdev@read
 igt@fbdev@write
 igt@gem_basic@bad-close
Signature · 6 lines
2.29.2

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
#14 lore raw

[igt-dev] ✓ Fi.CI.BAT: success for Test cases for fbdev

In reply to Thomas Zimmermann
== Series Details ==

== Series Details ==

Series: Test cases for fbdev
URL : https://patchwork.freedesktop.org/series/84103/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_9369 -> IGTPW_5201
====================================================

Summary
-------

**SUCCESS**

No regressions found.

External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/index.html

Possible new issues
-------------------

Here are the unknown changes that may have been introduced in IGTPW_5201:

### IGT changes ###

#### Possible regressions ####

* {igt@fbdev@read} (NEW):
- {fi-dg1-1}: NOTRUN -> [SKIP][1] +3 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-dg1-1/igt@[email protected]

New tests
---------

New tests have been introduced between CI_DRM_9369 and IGTPW_5201:

### New IGT tests (4) ###

* igt@fbdev@eof:
- Statuses : 37 pass(s) 4 skip(s)
- Exec time: [0.0, 0.00] s

* igt@fbdev@nullptr:
- Statuses : 37 pass(s) 4 skip(s)
- Exec time: [0.0, 0.01] s

* igt@fbdev@read:
- Statuses : 1 dmesg-warn(s) 36 pass(s) 4 skip(s)
- Exec time: [0.0, 3.06] s

* igt@fbdev@write:
- Statuses : 37 pass(s) 4 skip(s)
- Exec time: [0.0, 2.06] s

Known issues
------------

Here are the changes found in IGTPW_5201 that come from known issues:

### IGT changes ###

#### Issues hit ####

* igt@i915_getparams_basic@basic-subslice-total:
- fi-tgl-y: [PASS][2] -> [DMESG-WARN][3] ([i915#402]) +1 similar issue
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-tgl-y/igt@[email protected]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-tgl-y/igt@[email protected]

* igt@i915_module_load@reload:
- fi-icl-u2: [PASS][4] -> [DMESG-WARN][5] ([i915#1982]) +2 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-icl-u2/igt@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-icl-u2/igt@[email protected]
- fi-byt-j1900: [PASS][6] -> [DMESG-WARN][7] ([i915#1982])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-byt-j1900/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-byt-j1900/igt@[email protected]
- fi-skl-lmem: [PASS][8] -> [DMESG-WARN][9] ([i915#2605])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-skl-lmem/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-skl-lmem/igt@[email protected]
- fi-kbl-7500u: [PASS][10] -> [DMESG-WARN][11] ([i915#203])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-kbl-7500u/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-kbl-7500u/igt@[email protected]

#### Possible fixes ####

* igt@gem_exec_create@basic:
- fi-tgl-y: [DMESG-WARN][12] ([i915#402]) -> [PASS][13] +2 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-tgl-y/igt@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-tgl-y/igt@[email protected]

* igt@i915_module_load@reload:
- fi-bxt-dsi: [DMESG-WARN][14] ([i915#1635] / [i915#1982]) -> [PASS][15]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-bxt-dsi/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-bxt-dsi/igt@[email protected]

* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-bsw-kefka: [DMESG-WARN][16] ([i915#1982]) -> [PASS][17]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-bsw-kefka/igt@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-bsw-kefka/igt@[email protected]

* igt@kms_busy@basic@flip:
- fi-kbl-soraka: [DMESG-WARN][18] ([i915#1982]) -> [PASS][19]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-kbl-soraka/igt@kms_busy@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-kbl-soraka/igt@kms_busy@[email protected]

* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-byt-j1900: [DMESG-WARN][20] ([i915#1982]) -> [PASS][21]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-byt-j1900/igt@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-byt-j1900/igt@[email protected]

* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-icl-u2: [DMESG-WARN][22] ([i915#1982]) -> [PASS][23] +1 similar issue
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-icl-u2/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-icl-u2/igt@[email protected]

* igt@kms_force_connector_basic@force-connector-state:
- fi-tgl-y: [DMESG-WARN][24] ([i915#1982]) -> [PASS][25]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-tgl-y/igt@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-tgl-y/igt@[email protected]

#### Warnings ####

* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-tgl-y: [DMESG-WARN][26] ([i915#1982] / [i915#2411]) -> [DMESG-WARN][27] ([i915#2411])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/fi-tgl-y/igt@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/fi-tgl-y/igt@[email protected]

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#203]: https://gitlab.freedesktop.org/drm/intel/issues/203
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#2605]: https://gitlab.freedesktop.org/drm/intel/issues/2605
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402

Participating hosts (46 -> 41)
------------------------------

Missing (5): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-bdw-samus

Build changes
-------------

* CI: CI-20190529 -> None
* IGT: IGT_5863 -> IGTPW_5201

CI-20190529: 20190529
CI_DRM_9369: 50eb41aa12d68d1fff634d5f09a8faba3e72b46b @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5201: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/index.html
IGT_5863: 849de1780d33c6749e0a26dc3c642eb9b3d6cd42 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Testlist changes ==

+igt@fbdev@eof
+igt@fbdev@nullptr
+igt@fbdev@read
+igt@fbdev@unaligned-read
+igt@fbdev@unaligned-write
+igt@fbdev@write
-igt@fbdev@mmap

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/index.html

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#15 lore raw

[igt-dev] ✓ Fi.CI.IGT: success for Test cases for fbdev

In reply to Thomas Zimmermann
== Series Details ==

== Series Details ==

Series: Test cases for fbdev
URL : https://patchwork.freedesktop.org/series/84103/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_9369_full -> IGTPW_5201_full
====================================================

Summary
-------

**SUCCESS**

No regressions found.

External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/index.html

New tests
---------

New tests have been introduced between CI_DRM_9369_full and IGTPW_5201_full:

### New IGT tests (6) ###

* igt@fbdev@eof:
- Statuses : 7 pass(s)
- Exec time: [0.0] s

* igt@fbdev@nullptr:
- Statuses : 7 pass(s)
- Exec time: [0.0] s

* igt@fbdev@read:
- Statuses : 7 pass(s)
- Exec time: [0.07, 0.75] s

* igt@fbdev@unaligned-read:
- Statuses : 7 pass(s)
- Exec time: [0.00, 0.02] s

* igt@fbdev@unaligned-write:
- Statuses : 7 pass(s)
- Exec time: [0.02, 0.20] s

* igt@fbdev@write:
- Statuses : 7 pass(s)
- Exec time: [0.04, 0.41] s

Known issues
------------

Here are the changes found in IGTPW_5201_full that come from known issues:

### IGT changes ###

#### Issues hit ####

* igt@gem_exec_whisper@basic-queues-priority:
- shard-glk: [PASS][1] -> [DMESG-WARN][2] ([i915#118] / [i915#95])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk6/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk2/igt@[email protected]

* igt@i915_pm_rc6_residency@rc6-accuracy:
- shard-iclb: [PASS][3] -> [DMESG-WARN][4] ([i915#1982])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb3/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb2/igt@[email protected]

* igt@i915_pm_rpm@modeset-non-lpsp:
- shard-apl: [PASS][5] -> [SKIP][6] ([fdo#109271] / [i915#1635])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-apl4/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-apl1/igt@[email protected]
- shard-glk: [PASS][7] -> [SKIP][8] ([fdo#109271])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk4/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk2/igt@[email protected]
- shard-hsw: [PASS][9] -> [SKIP][10] ([fdo#109271])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-hsw7/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-hsw6/igt@[email protected]
- shard-kbl: [PASS][11] -> [SKIP][12] ([fdo#109271])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-kbl7/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-kbl1/igt@[email protected]

* igt@kms_big_fb@linear-64bpp-rotate-180:
- shard-glk: [PASS][13] -> [FAIL][14] ([i915#1119])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk4/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk9/igt@[email protected]

* igt@kms_cursor_edge_walk@pipe-a-64x64-bottom-edge:
- shard-glk: [PASS][15] -> [DMESG-WARN][16] ([i915#1982]) +3 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk6/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk9/igt@[email protected]

* igt@kms_cursor_edge_walk@pipe-c-64x64-left-edge:
- shard-hsw: [PASS][17] -> [DMESG-WARN][18] ([i915#1982]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-hsw8/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-hsw1/igt@[email protected]

* igt@kms_cursor_legacy@flip-vs-cursor-crc-atomic:
- shard-tglb: [PASS][19] -> [FAIL][20] ([i915#2346])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb7/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb3/igt@[email protected]

* igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
- shard-tglb: [PASS][21] -> [FAIL][22] ([i915#2598])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb2/igt@kms_flip@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb3/igt@kms_flip@[email protected]

* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-blt:
- shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([i915#1982]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-kbl7/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-kbl2/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-pgflip-blt:
- shard-apl: [PASS][25] -> [DMESG-WARN][26] ([i915#1635] / [i915#1982]) +2 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-apl7/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-apl6/igt@[email protected]

* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-onoff:
- shard-iclb: [PASS][27] -> [FAIL][28] ([i915#49])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb3/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb5/igt@[email protected]

* igt@kms_frontbuffer_tracking@psr-rgb565-draw-mmap-cpu:
- shard-tglb: [PASS][29] -> [DMESG-WARN][30] ([i915#1982]) +2 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb3/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb2/igt@[email protected]

* igt@kms_plane_lowres@pipe-a-tiling-none:
- shard-kbl: [PASS][31] -> [DMESG-WARN][32] ([i915#165] / [i915#78])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-kbl6/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-kbl2/igt@[email protected]

* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [PASS][33] -> [SKIP][34] ([fdo#109441]) +4 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb1/igt@kms_psr@psr2_sprite_plane_move.html

* igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
- shard-iclb: [PASS][35] -> [INCOMPLETE][36] ([i915#1185] / [i915#2405])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb8/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb3/igt@[email protected]
- shard-kbl: [PASS][37] -> [INCOMPLETE][38] ([i915#155] / [i915#2405])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-kbl6/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-kbl3/igt@[email protected]
- shard-hsw: [PASS][39] -> [INCOMPLETE][40] ([i915#2405] / [i915#2637])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-hsw7/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-hsw5/igt@[email protected]
- shard-glk: [PASS][41] -> [INCOMPLETE][42] ([i915#2405] / [i915#2635])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk4/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk5/igt@[email protected]
- shard-apl: [PASS][43] -> [INCOMPLETE][44] ([i915#1635] / [i915#2405] / [i915#2635])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-apl8/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-apl3/igt@[email protected]

* igt@prime_vgem@sync@rcs0:
- shard-tglb: [PASS][45] -> [INCOMPLETE][46] ([i915#409])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb2/igt@prime_vgem@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb6/igt@prime_vgem@[email protected]

#### Possible fixes ####

* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][47] ([i915#454]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb2/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb1/igt@[email protected]

* igt@i915_pm_rpm@dpms-mode-unset-non-lpsp:
- shard-hsw: [SKIP][49] ([fdo#109271]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-hsw8/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-hsw2/igt@[email protected]
- shard-kbl: [SKIP][51] ([fdo#109271]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-kbl3/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-kbl4/igt@[email protected]
- shard-apl: [SKIP][53] ([fdo#109271] / [i915#1635]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-apl7/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-apl7/igt@[email protected]
- shard-glk: [SKIP][55] ([fdo#109271]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk8/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk8/igt@[email protected]

* {igt@kms_async_flips@test-time-stamp}:
- shard-tglb: [FAIL][57] ([i915#2597]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb5/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb6/igt@[email protected]

* igt@kms_cursor_edge_walk@pipe-b-256x256-top-edge:
- shard-glk: [DMESG-WARN][59] ([i915#1982]) -> [PASS][60] +5 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk3/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk3/igt@[email protected]
- shard-apl: [DMESG-WARN][61] ([i915#1635] / [i915#1982]) -> [PASS][62] +4 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-apl4/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-apl2/igt@[email protected]

* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
- shard-hsw: [FAIL][63] ([i915#96]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-hsw8/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-hsw1/igt@[email protected]

* igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size:
- shard-hsw: [FAIL][65] ([i915#2295] / [i915#2370]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-hsw8/igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-hsw2/igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size.html

* igt@kms_cursor_legacy@cursor-vs-flip-varying-size:
- shard-hsw: [FAIL][67] ([i915#2370]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-hsw6/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-hsw6/igt@[email protected]

* igt@kms_flip@2x-flip-vs-absolute-wf_vblank@ab-vga1-hdmi-a1:
- shard-hsw: [DMESG-WARN][69] ([i915#1982]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-hsw6/igt@kms_flip@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-hsw5/igt@kms_flip@[email protected]

* igt@kms_flip@2x-plain-flip-fb-recreate@bc-hdmi-a1-hdmi-a2:
- shard-glk: [FAIL][71] ([i915#2122]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk4/igt@kms_flip@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk5/igt@kms_flip@[email protected]

* igt@kms_frontbuffer_tracking@psr-1p-primscrn-indfb-msflip-blt:
- shard-tglb: [DMESG-WARN][73] ([i915#1982]) -> [PASS][74] +3 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb3/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb7/igt@[email protected]

* igt@kms_psr@psr2_sprite_render:
- shard-iclb: [SKIP][75] ([fdo#109441]) -> [PASS][76]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb3/igt@kms_psr@psr2_sprite_render.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb2/igt@kms_psr@psr2_sprite_render.html

* igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
- shard-hsw: [INCOMPLETE][77] ([i915#2637]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-hsw8/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-hsw8/igt@[email protected]
- shard-kbl: [INCOMPLETE][79] ([i915#155]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-kbl3/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-kbl4/igt@[email protected]
- shard-iclb: [INCOMPLETE][81] ([i915#1185]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb5/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb6/igt@[email protected]
- shard-apl: [INCOMPLETE][83] ([i915#1635] / [i915#2635]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-apl7/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-apl2/igt@[email protected]
- shard-glk: [INCOMPLETE][85] ([i915#2635]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk8/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk3/igt@[email protected]

* igt@kms_vblank@pipe-b-wait-forked-busy:
- shard-kbl: [DMESG-WARN][87] ([i915#1982]) -> [PASS][88] +7 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-kbl3/igt@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-kbl2/igt@[email protected]

* igt@perf_pmu@module-unload:
- shard-tglb: [DMESG-WARN][89] ([i915#1982] / [i915#262]) -> [PASS][90]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb5/igt@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb8/igt@[email protected]

#### Warnings ####

* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: [WARN][91] ([i915#2684]) -> [WARN][92] ([i915#1804] / [i915#2684])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb3/igt@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb6/igt@[email protected]

* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [WARN][93] -> [WARN][94] ([i915#1804])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb5/igt@[email protected]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb3/igt@[email protected]

* igt@i915_pm_rpm@dpms-mode-unset-non-lpsp:
- shard-tglb: [SKIP][95] ([i915#579]) -> [SKIP][96] ([fdo#111644] / [i915#1397] / [i915#2411])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb3/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb2/igt@[email protected]
- shard-iclb: [SKIP][97] ([i915#579]) -> [SKIP][98] ([fdo#110892])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb5/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb2/igt@[email protected]

* igt@i915_pm_rpm@modeset-non-lpsp:
- shard-iclb: [SKIP][99] ([fdo#110892]) -> [SKIP][100] ([i915#579])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb3/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb7/igt@[email protected]
- shard-tglb: [SKIP][101] ([fdo#111644] / [i915#1397] / [i915#2411]) -> [SKIP][102] ([i915#579])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb1/igt@[email protected]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb3/igt@[email protected]

* igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
- shard-tglb: [INCOMPLETE][103] ([i915#1436] / [i915#1602] / [i915#1798] / [i915#1887] / [i915#1982] / [i915#2411] / [i915#456]) -> [DMESG-WARN][104] ([i915#2411])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb3/igt@[email protected]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb6/igt@[email protected]

* igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
- shard-tglb: [DMESG-WARN][105] ([i915#2411]) -> [INCOMPLETE][106] ([i915#1436] / [i915#1602] / [i915#1887] / [i915#2411] / [i915#456])
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb2/igt@[email protected]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb1/igt@[email protected]

* igt@kms_vblank@pipe-d-ts-continuation-dpms-rpm:
- shard-tglb: [DMESG-WARN][107] ([i915#2411]) -> [SKIP][108] ([i915#2648])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb2/igt@[email protected]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb1/igt@[email protected]

* igt@runner@aborted:
- shard-kbl: [FAIL][109] ([i915#2295] / [i915#483]) -> [FAIL][110] ([i915#2295])
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-kbl2/igt@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-kbl7/igt@[email protected]
- shard-iclb: ([FAIL][111], [FAIL][112]) ([i915#1814] / [i915#2295] / [i915#483]) -> ([FAIL][113], [FAIL][114]) ([i915#1814] / [i915#2295])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb8/igt@[email protected]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-iclb5/igt@[email protected]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb3/igt@[email protected]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-iclb4/igt@[email protected]
- shard-glk: ([FAIL][115], [FAIL][116]) ([i915#1814] / [i915#2295] / [k.org#202321]) -> ([FAIL][117], [FAIL][118]) ([i915#1814] / [i915#2295] / [i915#483] / [k.org#202321])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk6/igt@[email protected]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-glk8/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk7/igt@[email protected]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-glk5/igt@[email protected]
- shard-tglb: ([FAIL][119], [FAIL][120]) ([i915#1602] / [i915#2295]) -> ([FAIL][121], [FAIL][122], [FAIL][123]) ([i915#1602] / [i915#2295] / [i915#2426] / [i915#409])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb3/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9369/shard-tglb8/igt@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb6/igt@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb6/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/shard-tglb1/igt@[email protected]

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110892]: https://bugs.freedesktop.org/show_bug.cgi?id=110892
[fdo#111644]: https://bugs.freedesktop.org/show_bug.cgi?id=111644
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1185]: https://gitlab.freedesktop.org/drm/intel/issues/1185
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#1798]: https://gitlab.freedesktop.org/drm/intel/issues/1798
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#1887]: https://gitlab.freedesktop.org/drm/intel/issues/1887
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2295]: https://gitlab.freedesktop.org/drm/intel/issues/2295
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2370]: https://gitlab.freedesktop.org/drm/intel/issues/2370
[i915#2405]: https://gitlab.freedesktop.org/drm/intel/issues/2405
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#2426]: https://gitlab.freedesktop.org/drm/intel/issues/2426
[i915#2597]: https://gitlab.freedesktop.org/drm/intel/issues/2597
[i915#2598]: https://gitlab.freedesktop.org/drm/intel/issues/2598
[i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262
[i915#2635]: https://gitlab.freedesktop.org/drm/intel/issues/2635
[i915#2637]: https://gitlab.freedesktop.org/drm/intel/issues/2637
[i915#2641]: https://gitlab.freedesktop.org/drm/intel/issues/2641
[i915#2648]: https://gitlab.freedesktop.org/drm/intel/issues/2648
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#409]: https://gitlab.freedesktop.org/drm/intel/issues/409
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456
[i915#483]: https://gitlab.freedesktop.org/drm/intel/issues/483
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#579]: https://gitlab.freedesktop.org/drm/intel/issues/579
[i915#78]: https://gitlab.freedesktop.org/drm/intel/issues/78
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[i915#96]: https://gitlab.freedesktop.org/drm/intel/issues/96
[k.org#202321]: https://bugzilla.kernel.org/show_bug.cgi?id=202321

Participating hosts (10 -> 8)
------------------------------

Missing (2): pig-skl-6260u pig-glk-j5005

Build changes
-------------

* CI: CI-20190529 -> None
* IGT: IGT_5863 -> IGTPW_5201
* Piglit: piglit_4509 -> None

CI-20190529: 20190529
CI_DRM_9369: 50eb41aa12d68d1fff634d5f09a8faba3e72b46b @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5201: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/index.html
IGT_5863: 849de1780d33c6749e0a26dc3c642eb9b3d6cd42 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5201/index.html

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev