Skip to contentSkip to conversation

runner: Inject a message when killing test to taints

PATCH In review Petri Latvala 3 participants 10 messages Jun 18, 2020

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 runner: Inject a message when killing test to taints

Normally runner injecting a message to the test's stdout/stderr logs has a race condition; The test outputs have special lines (subtest starting/ending) and accidentally injecting stuff in between would cause funky results.

When we're killing a test because the kernel got tainted, we know already that we're not getting a subtest ending line and we can inject, if we make sure we have newlines printed before and after the injection.

Having a message in the stdout of the test will aid automatic bug filtering.

Cc Arkadiusz Hiler <[email protected]>
---
 runner/executor.c | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)
runner/executor.c +19 -1
index 06390262..7bb2b14c 100644
@@ -1049,9 +1049,27 @@ static int monitor_output(pid_t child,
 				 * the result an incomplete we avoid
 				 * journaling a timeout here.
 				 */
-				if (is_tainted(taints))
+				if (is_tainted(taints)) {
 					exitline = EXECUTOR_EXIT;
 
+					/*
+					 * Also inject a message to
+					 * the test's stdout. As we're
+					 * shooting for an incomplete
+					 * anyway, we don't need to
+					 * care if we're not between
+					 * full lines from stdout. We
+					 * do need to make sure we
+					 * have newlines on both ends
+					 * of this injection though.
+					 */
+					dprintf(outputs[_F_OUT],
+						"\nrunner: This test was killed due to a kernel taint (0x%lx).\n",
+						taints);
+					if (settings->sync)
+						fdatasync(outputs[_F_OUT]);
+				}
+
 				dprintf(outputs[_F_JOURNAL], "%s%d (%.3fs)\n",
 					exitline,
 					status, time);
Signature · 6 lines
2.20.1

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

PATCH 2/2 runner: Introduce --disk-usage-limit

Disk usage limit is a limit of disk space taken, per (dynamic) subtest. If the test's output, kernel log included, exceeds this limit, the test is killed, similarly to killing the test when the kernel gets tainted.

Cc Arkadiusz Hiler <[email protected]>
---
 runner/executor.c     | 55 ++++++++++++++++++++++++++++++++++++-------
 runner/runner_tests.c | 28 ++++++++++++++++++++++
 runner/settings.c     | 55 +++++++++++++++++++++++++++++++++++++++++++
 runner/settings.h     |  1 +
 4 files changed, 130 insertions(+), 9 deletions(-)
runner/executor.c +46 -9
index 7bb2b14c..25e37bff 100644
@@ -540,7 +540,8 @@ void close_outputs(int *fds)
 	}
 }
 
-static int dump_dmesg(int kmsgfd, int outfd)
+/* Returns the number of bytes written to disk, or a negative number on error */
+static long dump_dmesg(int kmsgfd, int outfd)
 {
 	/*
 	 * Write kernel messages to the log file until we reach
@@ -556,6 +557,7 @@ static int dump_dmesg(int kmsgfd, int outfd)
 	char cont;
 	char buf[2048];
 	ssize_t r;
+	long written = 0;
 
 	if (kmsgfd < 0)
 		return 0;
@@ -600,15 +602,16 @@ static int dump_dmesg(int kmsgfd, int outfd)
 				continue;
 			} else if (errno != EAGAIN) {
 				errf("Error reading from kmsg: %m\n");
-				return errno;
+				return -errno;
 			}
 
 			/* EAGAIN, so we're done dumping */
 			close(comparefd);
-			return 0;
+			return written;
 		}
 
 		write(outfd, buf, r);
+		written += r;
 
 		if (comparefd < 0 && sscanf(buf, "%u,%llu,%llu,%c;",
 					    &flags, &seq, &usec, &cont) == 4) {
@@ -618,7 +621,7 @@ static int dump_dmesg(int kmsgfd, int outfd)
 			 * enough.
 			 */
 			if (seq >= cmpseq)
-				return 0;
+				return written;
 		}
 	}
 }
@@ -708,12 +711,20 @@ static const char *show_kernel_task_state(const char *msg)
 	return msg;
 }
 
+static bool disk_usage_limit_exceeded(struct settings *settings,
+				      size_t disk_usage)
+{
+	return settings->disk_usage_limit != 0 &&
+		disk_usage > settings->disk_usage_limit;
+}
+
 static const char *need_to_timeout(struct settings *settings,
 				   int killed,
 				   unsigned long taints,
 				   double time_since_activity,
 				   double time_since_subtest,
-				   double time_since_kill)
+				   double time_since_kill,
+				   size_t disk_usage)
 {
 	if (killed) {
 		/*
@@ -757,6 +768,9 @@ static const char *need_to_timeout(struct settings *settings,
 	    time_since_activity > settings->inactivity_timeout)
 		return show_kernel_task_state("Inactivity timeout exceeded. Killing the current test with SIGQUIT.\n");
 
+	if (disk_usage_limit_exceeded(settings, disk_usage))
+		return "Disk usage limit exceeded.\n";
+
 	return NULL;
 }
 
@@ -801,6 +815,7 @@ static int monitor_output(pid_t child,
 	struct timespec time_beg, time_now, time_last_activity, time_last_subtest, time_killed;
 	unsigned long taints = 0;
 	bool aborting = false;
+	size_t disk_usage = 0;
 
 	igt_gettime(&time_beg);
 	time_last_activity = time_last_subtest = time_killed = time_beg;
@@ -878,6 +893,7 @@ static int monitor_output(pid_t child,
 			}
 
 			write(outputs[_F_OUT], buf, s);
+			disk_usage += s;
 			if (settings->sync) {
 				fdatasync(outputs[_F_OUT]);
 			}
@@ -901,6 +917,7 @@ static int monitor_output(pid_t child,
 					current_subtest[linelen - strlen(STARTING_SUBTEST)] = '\0';
 
 					time_last_subtest = time_now;
+					disk_usage = s;
 
 					if (settings->log_level >= LOG_LEVEL_VERBOSE) {
 						fwrite(outbuf, 1, linelen, stdout);
@@ -933,6 +950,7 @@ static int monitor_output(pid_t child,
 				if (linelen > strlen(STARTING_DYNAMIC_SUBTEST) &&
 				    !memcmp(outbuf, STARTING_DYNAMIC_SUBTEST, strlen(STARTING_DYNAMIC_SUBTEST))) {
 					time_last_subtest = time_now;
+					disk_usage = s;
 
 					if (settings->log_level >= LOG_LEVEL_VERBOSE) {
 						fwrite(outbuf, 1, linelen, stdout);
@@ -967,6 +985,7 @@ static int monitor_output(pid_t child,
 				errfd = -1;
 			} else {
 				write(outputs[_F_ERR], buf, s);
+				disk_usage += s;
 				if (settings->sync) {
 					fdatasync(outputs[_F_ERR]);
 				}
@@ -974,17 +993,19 @@ static int monitor_output(pid_t child,
 		}
 
 		if (kmsgfd >= 0 && FD_ISSET(kmsgfd, &set)) {
-			int dmesgstatus;
+			long dmesgwritten;
 
 			time_last_activity = time_now;
 
-			dmesgstatus = dump_dmesg(kmsgfd, outputs[_F_DMESG]);
+			dmesgwritten = dump_dmesg(kmsgfd, outputs[_F_DMESG]);
 			if (settings->sync)
 				fdatasync(outputs[_F_DMESG]);
 
-			if (dmesgstatus) {
+			if (dmesgwritten < 0) {
 				close(kmsgfd);
 				kmsgfd = -1;
+			} else {
+				disk_usage += dmesgwritten;
 			}
 		}
 
@@ -1070,6 +1091,21 @@ static int monitor_output(pid_t child,
 						fdatasync(outputs[_F_OUT]);
 				}
 
+				/*
+				 * Same goes for stopping because we
+				 * exceeded the disk usage limit.
+				 */
+				if (disk_usage_limit_exceeded(settings, disk_usage)) {
+					exitline = EXECUTOR_EXIT;
+					dprintf(outputs[_F_OUT],
+						"\nrunner: This test was killed due to exceeding disk usage limit. "
+						"(Used %zd bytes, limit %zd)\n",
+						disk_usage,
+						settings->disk_usage_limit);
+					if (settings->sync)
+						fdatasync(outputs[_F_OUT]);
+				}
+
 				dprintf(outputs[_F_JOURNAL], "%s%d (%.3fs)\n",
 					exitline,
 					status, time);
@@ -1091,7 +1127,8 @@ static int monitor_output(pid_t child,
 		timeout_reason = need_to_timeout(settings, killed, tainted(&taints),
 						 igt_time_elapsed(&time_last_activity, &time_now),
 						 igt_time_elapsed(&time_last_subtest, &time_now),
-						 igt_time_elapsed(&time_killed, &time_now));
+						 igt_time_elapsed(&time_killed, &time_now),
+						 disk_usage);
 
 		if (timeout_reason) {
 			if (killed == SIGKILL) {
runner/runner_tests.c +28 -0
index 48b02107..cd033f6c 100644
@@ -183,6 +183,7 @@ static void assert_settings_equal(struct settings *one, struct settings *two)
 	 * here.
 	 */
 	igt_assert_eq(one->abort_mask, two->abort_mask);
+	igt_assert_eq_u64(one->disk_usage_limit, two->disk_usage_limit);
 	igt_assert_eqstr(one->test_list, two->test_list);
 	igt_assert_eqstr(one->name, two->name);
 	igt_assert_eq(one->dry_run, two->dry_run);
@@ -270,6 +271,7 @@ igt_main
 		igt_assert(parse_options(ARRAY_SIZE(argv), (char**)argv, settings));
 
 		igt_assert_eq(settings->abort_mask, 0);
+		igt_assert_eq_u64(settings->disk_usage_limit, 0UL);
 		igt_assert(!settings->test_list);
 		igt_assert_eqstr(settings->name, "path-to-results");
 		igt_assert(!settings->dry_run);
@@ -415,6 +417,7 @@ igt_main
 		const char *argv[] = { "runner",
 				       "-n", "foo",
 				       "--abort-on-monitored-error=taint,lockdep",
+				       "--disk-usage-limit=4096",
 				       "--test-list", "path-to-test-list",
 				       "--ignore-missing",
 				       "--dry-run",
@@ -444,6 +447,7 @@ igt_main
 		igt_assert(parse_options(ARRAY_SIZE(argv), (char**)argv, settings));
 
 		igt_assert_eq(settings->abort_mask, ABORT_TAINT | ABORT_LOCKDEP);
+		igt_assert_eq_u64(settings->disk_usage_limit, 4096UL);
 		igt_assert(strstr(settings->test_list, "path-to-test-list") != NULL);
 		igt_assert_eqstr(settings->name, "foo");
 		igt_assert(settings->dry_run);
@@ -592,6 +596,29 @@ igt_main
 
 	}
 
+	igt_subtest("disk-usage-limit-suffixes") {
+		const char *argv[] = { "runner",
+				       "--disk-usage-limit=4096",
+				       "test-root-dir",
+				       "results-path",
+		};
+
+		igt_assert(parse_options(ARRAY_SIZE(argv), (char**)argv, settings));
+		igt_assert_eq_u64(settings->disk_usage_limit, 4096UL);
+
+		argv[1] = "--disk-usage-limit=4k";
+		igt_assert(parse_options(ARRAY_SIZE(argv), (char**)argv, settings));
+		igt_assert_eq_u64(settings->disk_usage_limit, 4096UL);
+
+		argv[1] = "--disk-usage-limit=1M";
+		igt_assert(parse_options(ARRAY_SIZE(argv), (char**)argv, settings));
+		igt_assert_eq_u64(settings->disk_usage_limit, 1024UL * 1024UL);
+
+		argv[1] = "--disk-usage-limit=1G";
+		igt_assert(parse_options(ARRAY_SIZE(argv), (char**)argv, settings));
+		igt_assert_eq_u64(settings->disk_usage_limit, 1024UL * 1024UL * 1024UL);
+	}
+
 	igt_subtest("parse-clears-old-data") {
 		const char *argv[] = { "runner",
 				       "-n", "foo",
@@ -838,6 +865,7 @@ igt_main
 			const char *argv[] = { "runner",
 					       "-n", "foo",
 					       "--abort-on-monitored-error",
+					       "--disk-usage-limit=4k",
 					       "--test-list", "path-to-test-list",
 					       "--ignore-missing",
 					       "--dry-run",
runner/settings.c +55 -0

97 lines not on this page · raw message

runner/settings.h +1 -0
index 5203ec6e..409391f9 100644
@@ -28,6 +28,7 @@ struct regex_list {
 
 struct settings {
 	int abort_mask;
+	size_t disk_usage_limit;
 	char *test_list;
 	char *name;
 	bool dry_run;
Signature · 6 lines
2.20.1

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

Re: [igt-dev] [PATCH i-g-t 2/2] runner: Introduce --disk-usage-limit

Quoted 4 lines · Petri Latvala

Disk usage limit is a limit of disk space taken, per (dynamic) subtest. If the test's output, kernel log included, exceeds this limit, the test is killed, similarly to killing the test when the kernel gets tainted.

So this is a combined limit, i.e. shared by stderr, stdout and dmesg, right?

Also since this is handled by need_to_timeout, will the final test result be a timeout?

Any particular reason why we are killing the test instead of just appending a message that output was truncated and letting the test be?

When we were talking about this I had imagined something more like:

1. size limit per logged file
2. test finishes execution
3. the logs state that the test was spammy and we truncated the logs
4. "promote" passes to warns in such cases

No strong feeling on which option we will go with, but I would like to understand why you went in that way.

Signature · 6 lines
Cheers,
Arek
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
#3 lore raw

Re: [igt-dev] [PATCH i-g-t 2/2] runner: Introduce --disk-usage-limit

Quoted 8 lines · Arkadiusz Hiler
Quoted 4 lines · Petri Latvala

Disk usage limit is a limit of disk space taken, per (dynamic) subtest. If the test's output, kernel log included, exceeds this limit, the test is killed, similarly to killing the test when the kernel gets tainted.

So this is a combined limit, i.e. shared by stderr, stdout and dmesg, right?

Yes, combined limit.

Quoted 2 lines

Also since this is handled by need_to_timeout, will the final test result be a timeout?

It will be an incomplete. With an injection in the stdout, like when killing for taints, for automatic filtering.

Quoted 5 lines

Any particular reason why we are killing the test instead of just appending a message that output was truncated and letting the test be?

When we were talking about this I had imagined something more like:

Quoted 7 lines

1. size limit per logged file
2. test finishes execution
3. the logs state that the test was spammy and we truncated the logs
4. "promote" passes to warns in such cases

No strong feeling on which option we will go with, but I would like to understand why you went in that way.

In my opinion it's a waste of disk space on the DUT; There shouldn't be a case where having "too much" (tm) stuff logged is considered normal. And if we accept that, we might as well also save some time by killing the test when we go over.

Truncating the logs is possible but way more code; Instead of just finding the delimit offsets in the stdout file and stuffing that range to the json string object, you need to construct a new string, making sure you avoid cutting out the subtest result line. I repeat:
Possible, almost easy. Just more code in an already complex resultgen codebase for doing a simple thing :P

So in a nutshell: The approach depends on whether spamming logs is considered "just a warn" or "oh, please no".

Signature · 5 lines
Petri Latvala
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Reviewed-by
#4 lore raw

Re: [igt-dev] [PATCH i-g-t 2/2] runner: Introduce --disk-usage-limit

Quoted 43 lines · Petri Latvala
Quoted 8 lines · Arkadiusz Hiler
Quoted 4 lines · Petri Latvala

Disk usage limit is a limit of disk space taken, per (dynamic) subtest. If the test's output, kernel log included, exceeds this limit, the test is killed, similarly to killing the test when the kernel gets tainted.

So this is a combined limit, i.e. shared by stderr, stdout and dmesg, right?

Yes, combined limit.

Quoted 2 lines

Also since this is handled by need_to_timeout, will the final test result be a timeout?

It will be an incomplete. With an injection in the stdout, like when killing for taints, for automatic filtering.

Quoted 5 lines

Any particular reason why we are killing the test instead of just appending a message that output was truncated and letting the test be?

When we were talking about this I had imagined something more like:

Quoted 7 lines

1. size limit per logged file
2. test finishes execution
3. the logs state that the test was spammy and we truncated the logs
4. "promote" passes to warns in such cases

No strong feeling on which option we will go with, but I would like to understand why you went in that way.

In my opinion it's a waste of disk space on the DUT; There shouldn't be a case where having "too much" (tm) stuff logged is considered normal. And if we accept that, we might as well also save some time by killing the test when we go over.

Truncating the logs is possible but way more code; Instead of just finding the delimit offsets in the stdout file and stuffing that range to the json string object, you need to construct a new string, making sure you avoid cutting out the subtest result line. I repeat:
Possible, almost easy. Just more code in an already complex resultgen codebase for doing a simple thing :P

Quoted 2 lines

So in a nutshell: The approach depends on whether spamming logs is considered "just a warn" or "oh, please no".

I'll take one "oh, please no".

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

Reviewed-by on v1 1/2
#5 lore raw
In reply to Petri Latvala
Quoted 10 lines · Petri Latvala

Normally runner injecting a message to the test's stdout/stderr logs has a race condition; The test outputs have special lines (subtest starting/ending) and accidentally injecting stuff in between would cause funky results.

When we're killing a test because the kernel got tainted, we know already that we're not getting a subtest ending line and we can inject, if we make sure we have newlines printed before and after the injection.

Quoted 5 lines

Having a message in the stdout of the test will aid automatic bug filtering.

Cc Arkadiusz Hiler <[email protected]>

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

#6 lore raw

[igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] runner: Inject a message when killing test to taints

In reply to Petri Latvala
== Series Details ==

== Series Details ==

Series: series starting with [i-g-t,1/2] runner: Inject a message when killing test to taints
URL : https://patchwork.freedesktop.org/series/78526/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_8641 -> IGTPW_4683
====================================================

Summary
-------

**SUCCESS**

No regressions found.

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

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

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

### IGT changes ###

#### Suppressed ####

The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.

* igt@i915_selftest@live@execlists:
- {fi-tgl-dsi}: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-tgl-dsi/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-tgl-dsi/igt@i915_selftest@[email protected]

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

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

### IGT changes ###

#### Issues hit ####

* igt@gem_exec_suspend@basic-s0:
- fi-apl-guc: [PASS][3] -> [INCOMPLETE][4] ([i915#1242])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-apl-guc/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-apl-guc/igt@[email protected]

* igt@i915_pm_rpm@module-reload:
- fi-glk-dsi: [PASS][5] -> [DMESG-WARN][6] ([i915#1982])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-glk-dsi/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-glk-dsi/igt@[email protected]

* igt@kms_cursor_legacy@basic-flip-after-cursor-atomic:
- fi-icl-guc: [PASS][7] -> [DMESG-WARN][8] ([i915#1982]) +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-icl-guc/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-icl-guc/igt@[email protected]

* igt@kms_cursor_legacy@basic-flip-after-cursor-legacy:
- fi-icl-u2: [PASS][9] -> [DMESG-WARN][10] ([i915#1982])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-icl-u2/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-icl-u2/igt@[email protected]

* igt@kms_pipe_crc_basic@read-crc-pipe-a-frame-sequence:
- fi-tgl-u2: [PASS][11] -> [DMESG-WARN][12] ([i915#402])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-tgl-u2/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-tgl-u2/igt@[email protected]

#### Possible fixes ####

* igt@gem_exec_suspend@basic-s0:
- fi-tgl-u2: [FAIL][13] ([i915#1888]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-tgl-u2/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-tgl-u2/igt@[email protected]

* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-byt-j1900: [DMESG-WARN][15] ([i915#1982]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-byt-j1900/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-byt-j1900/igt@[email protected]

* igt@i915_selftest@live@gt_lrc:
- fi-tgl-u2: [DMESG-FAIL][17] ([i915#1233]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-tgl-u2/igt@i915_selftest@live@gt_lrc.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-tgl-u2/igt@i915_selftest@live@gt_lrc.html

* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- {fi-kbl-7560u}: [DMESG-WARN][19] ([i915#1982]) -> [PASS][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-kbl-7560u/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-kbl-7560u/igt@[email protected]

* igt@kms_flip@basic-flip-vs-modeset@d-dsi1:
- {fi-tgl-dsi}: [DMESG-WARN][21] ([i915#1982]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-tgl-dsi/igt@kms_flip@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-tgl-dsi/igt@kms_flip@[email protected]

#### Warnings ####

* igt@gem_exec_suspend@basic-s0:
- fi-kbl-x1275: [DMESG-WARN][23] ([i915#62] / [i915#92]) -> [DMESG-WARN][24] ([i915#62] / [i915#92] / [i915#95]) +8 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-kbl-x1275/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-kbl-x1275/igt@[email protected]

* igt@kms_cursor_legacy@basic-flip-before-cursor-varying-size:
- fi-kbl-x1275: [DMESG-WARN][25] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][26] ([i915#62] / [i915#92]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-kbl-x1275/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-kbl-x1275/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#1233]: https://gitlab.freedesktop.org/drm/intel/issues/1233
[i915#1242]: https://gitlab.freedesktop.org/drm/intel/issues/1242
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95

Participating hosts (49 -> 40)
------------------------------

Missing (9): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-skl-lmem fi-bdw-samus fi-byt-clapper fi-skl-6700k2

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

* CI: CI-20190529 -> None
* IGT: IGT_5712 -> IGTPW_4683

CI-20190529: 20190529
CI_DRM_8641: aac91f91c7be78f53b352237d968dfa1996b2d4b @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4683: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/index.html
IGT_5712: eba1135ddd35f9d3097ed91032aefe8f9a9f9d02 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#7 lore raw

Re: [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] runner: Inject a message when killing test to taints

Quoted 29 lines · Patchwork

== Series Details ==

Series: series starting with [i-g-t,1/2] runner: Inject a message when killing test to taints
URL : https://patchwork.freedesktop.org/series/78526/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_8641 -> IGTPW_4683
====================================================

Summary
-------

**SUCCESS**

No regressions found.

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

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

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

### IGT changes ###

#### Suppressed ####

Quoted 7 lines

The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.

* igt@i915_selftest@live@execlists:
- {fi-tgl-dsi}: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/fi-tgl-dsi/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/fi-tgl-dsi/igt@i915_selftest@[email protected]

Ah, a good example of the taint-injection!

Signature · 5 lines
Petri Latvala
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
#8 lore raw

[igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/2] runner: Inject a message when killing test to taints

In reply to Petri Latvala
== Series Details ==

== Series Details ==

Series: series starting with [i-g-t,1/2] runner: Inject a message when killing test to taints
URL : https://patchwork.freedesktop.org/series/78526/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_8641_full -> IGTPW_4683_full
====================================================

Summary
-------

**FAILURE**

Serious unknown changes coming with IGTPW_4683_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in IGTPW_4683_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

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

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

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

### IGT changes ###

#### Possible regressions ####

* igt@kms_flip@2x-blocking-absolute-wf_vblank-interruptible@ab-vga1-hdmi-a1:
- shard-hsw: [PASS][1] -> [INCOMPLETE][2] +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-hsw6/igt@kms_flip@2x-blocking-absolute-wf_vblank-interruptible@ab-vga1-hdmi-a1.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-hsw2/igt@kms_flip@2x-blocking-absolute-wf_vblank-interruptible@ab-vga1-hdmi-a1.html

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

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

### IGT changes ###

#### Issues hit ####

* igt@gem_exec_create@forked:
- shard-glk: [PASS][3] -> [DMESG-WARN][4] ([i915#118] / [i915#95]) +2 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-glk1/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-glk5/igt@[email protected]

* igt@gem_exec_schedule@implicit-read-write@bcs0:
- shard-snb: [PASS][5] -> [INCOMPLETE][6] ([i915#82])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-snb4/igt@gem_exec_schedule@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-snb2/igt@gem_exec_schedule@[email protected]

* igt@gem_exec_suspend@basic-s3:
- shard-kbl: [PASS][7] -> [DMESG-WARN][8] ([i915#180])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl2/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl4/igt@[email protected]
- shard-snb: [PASS][9] -> [DMESG-WARN][10] ([i915#42])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-snb5/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-snb4/igt@[email protected]

* igt@gem_shrink@reclaim:
- shard-hsw: [PASS][11] -> [SKIP][12] ([fdo#109271])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-hsw8/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-hsw7/igt@[email protected]

* igt@kms_big_fb@linear-64bpp-rotate-0:
- shard-glk: [PASS][13] -> [DMESG-FAIL][14] ([i915#118] / [i915#95])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-glk6/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-glk8/igt@[email protected]

* igt@kms_color@pipe-a-ctm-red-to-blue:
- shard-tglb: [PASS][15] -> [DMESG-WARN][16] ([i915#1149] / [i915#402])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-tglb7/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-tglb3/igt@[email protected]

* igt@kms_cursor_crc@pipe-a-cursor-256x85-random:
- shard-kbl: [PASS][17] -> [DMESG-FAIL][18] ([i915#54] / [i915#95]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl3/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl7/igt@[email protected]

* igt@kms_draw_crc@draw-method-xrgb8888-mmap-wc-ytiled:
- shard-apl: [PASS][19] -> [DMESG-WARN][20] ([i915#95]) +41 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl3/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl2/igt@[email protected]

* igt@kms_flip@flip-vs-expired-vblank@c-dp1:
- shard-apl: [PASS][21] -> [FAIL][22] ([i915#79])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl8/igt@kms_flip@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl2/igt@kms_flip@[email protected]

* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-gtt:
- shard-tglb: [PASS][23] -> [DMESG-WARN][24] ([i915#1982]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-tglb2/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-tglb5/igt@[email protected]

* igt@kms_pipe_crc_basic@hang-read-crc-pipe-a:
- shard-kbl: [PASS][25] -> [DMESG-FAIL][26] ([i915#95]) +2 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl4/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl1/igt@[email protected]

* igt@kms_pipe_crc_basic@read-crc-pipe-a:
- shard-apl: [PASS][27] -> [DMESG-FAIL][28] ([i915#95]) +2 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl4/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl1/igt@[email protected]

* igt@kms_plane_cursor@pipe-a-primary-size-128:
- shard-kbl: [PASS][29] -> [DMESG-WARN][30] ([i915#93] / [i915#95]) +50 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl4/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl1/igt@[email protected]

* igt@kms_plane_multiple@atomic-pipe-d-tiling-none:
- shard-tglb: [PASS][31] -> [DMESG-WARN][32] ([i915#402]) +3 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-tglb1/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-tglb8/igt@[email protected]

* igt@kms_psr@psr2_primary_render:
- shard-iclb: [PASS][33] -> [SKIP][34] ([fdo#109441])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-iclb2/igt@kms_psr@psr2_primary_render.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-iclb7/igt@kms_psr@psr2_primary_render.html

* igt@kms_setmode@basic:
- shard-apl: [PASS][35] -> [FAIL][36] ([i915#31])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl1/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl1/igt@[email protected]

#### Possible fixes ####

* igt@gem_exec_reloc@basic-concurrent0:
- shard-glk: [FAIL][37] ([i915#1930]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-glk5/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-glk1/igt@[email protected]

* igt@gem_exec_schedule@implicit-write-read@rcs0:
- shard-snb: [INCOMPLETE][39] ([i915#82]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-snb2/igt@gem_exec_schedule@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-snb1/igt@gem_exec_schedule@[email protected]

* igt@gem_exec_whisper@basic-contexts-all:
- shard-glk: [DMESG-WARN][41] ([i915#118] / [i915#95]) -> [PASS][42] +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-glk7/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-glk5/igt@[email protected]

* igt@gem_fence_thrash@bo-write-verify-threaded-none:
- shard-snb: [TIMEOUT][43] ([i915#1958]) -> [PASS][44] +3 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-snb1/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-snb4/igt@[email protected]

* igt@i915_suspend@debugfs-reader:
- shard-tglb: [INCOMPLETE][45] ([i915#1602] / [i915#456]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-tglb3/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-tglb6/igt@[email protected]

* igt@kms_addfb_basic@bad-pitch-128:
- shard-hsw: [TIMEOUT][47] ([i915#1958]) -> [PASS][48] +4 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-hsw4/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-hsw4/igt@[email protected]

* {igt@kms_atomic_transition@plane-all-transition@hdmi-a-1-pipe-a}:
- shard-glk: [INCOMPLETE][49] ([i915#58] / [k.org#198133]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-glk8/igt@kms_atomic_transition@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-glk2/igt@kms_atomic_transition@[email protected]

* igt@kms_cursor_crc@pipe-c-cursor-256x85-sliding:
- shard-apl: [FAIL][51] ([i915#54]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl3/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl1/igt@[email protected]

* igt@kms_draw_crc@draw-method-xrgb8888-mmap-gtt-xtiled:
- shard-kbl: [DMESG-WARN][53] ([i915#93] / [i915#95]) -> [PASS][54] +39 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl3/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl3/igt@[email protected]

* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: [DMESG-WARN][55] ([i915#180]) -> [PASS][56] +9 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl2/igt@kms_flip@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl7/igt@kms_flip@[email protected]

* igt@kms_flip@plain-flip-fb-recreate@a-dp1:
- shard-kbl: [DMESG-WARN][57] ([i915#1982]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl4/igt@kms_flip@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl4/igt@kms_flip@[email protected]

* igt@kms_flip_tiling@flip-x-tiled:
- shard-apl: [DMESG-WARN][59] ([i915#95]) -> [PASS][60] +35 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl6/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl2/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-badstride:
- shard-glk: [DMESG-WARN][61] ([i915#1982]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-glk9/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-glk9/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-mmap-gtt:
- shard-tglb: [DMESG-WARN][63] ([i915#1982]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-tglb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-mmap-gtt.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-tglb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-mmap-gtt.html

* igt@kms_plane_alpha_blend@pipe-a-coverage-vs-premult-vs-constant:
- shard-kbl: [DMESG-FAIL][65] ([fdo#108145] / [i915#95]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl1/igt@kms_plane_alpha_blend@pipe-a-coverage-vs-premult-vs-constant.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl6/igt@kms_plane_alpha_blend@pipe-a-coverage-vs-premult-vs-constant.html
- shard-apl: [DMESG-FAIL][67] ([fdo#108145] / [i915#95]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl4/igt@kms_plane_alpha_blend@pipe-a-coverage-vs-premult-vs-constant.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl2/igt@kms_plane_alpha_blend@pipe-a-coverage-vs-premult-vs-constant.html

* igt@kms_psr@psr2_sprite_plane_onoff:
- shard-iclb: [SKIP][69] ([fdo#109441]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-iclb3/igt@kms_psr@psr2_sprite_plane_onoff.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-iclb2/igt@kms_psr@psr2_sprite_plane_onoff.html

* igt@perf_pmu@semaphore-busy@rcs0:
- shard-kbl: [FAIL][71] ([i915#1820] / [i915#93] / [i915#95]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl7/igt@perf_pmu@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl2/igt@perf_pmu@[email protected]

#### Warnings ####

* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][73] ([i915#1899]) -> [FAIL][74] ([i915#454])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-iclb8/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-iclb6/igt@[email protected]
- shard-tglb: [SKIP][75] ([i915#468]) -> [FAIL][76] ([i915#454])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-tglb2/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-tglb3/igt@[email protected]

* igt@kms_color_chamelium@pipe-d-ctm-green-to-red:
- shard-hsw: [SKIP][77] ([fdo#109271] / [fdo#111827]) -> [TIMEOUT][78] ([i915#1958])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-hsw2/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-hsw6/igt@[email protected]
- shard-snb: [SKIP][79] ([fdo#109271] / [fdo#111827]) -> [TIMEOUT][80] ([i915#1958])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-snb4/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-snb6/igt@[email protected]

* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][81] ([fdo#110321] / [fdo#110336]) -> [DMESG-FAIL][82] ([fdo#110321] / [i915#95])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl2/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl4/igt@[email protected]

* igt@kms_content_protection@lic:
- shard-apl: [FAIL][83] ([fdo#110321]) -> [DMESG-FAIL][84] ([fdo#110321] / [i915#95])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl4/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl8/igt@[email protected]

* igt@kms_cursor_crc@pipe-d-cursor-256x256-onscreen:
- shard-hsw: [SKIP][85] ([fdo#109271]) -> [TIMEOUT][86] ([i915#1958]) +3 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-hsw2/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-hsw6/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt:
- shard-apl: [DMESG-FAIL][87] ([i915#49] / [i915#95]) -> [DMESG-WARN][88] ([i915#95])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl8/igt@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl4/igt@[email protected]
- shard-kbl: [FAIL][89] ([i915#49]) -> [DMESG-WARN][90] ([i915#93] / [i915#95])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl7/igt@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl2/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbcpsr-rgb565-draw-blt:
- shard-snb: [SKIP][91] ([fdo#109271]) -> [TIMEOUT][92] ([i915#1958]) +3 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-snb2/igt@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-snb6/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- shard-apl: [FAIL][93] ([fdo#108145] / [i915#265]) -> [DMESG-FAIL][94] ([fdo#108145] / [i915#95]) +1 similar issue
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-apl2/igt@[email protected]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-apl8/igt@[email protected]
- shard-kbl: [FAIL][95] ([fdo#108145] / [i915#265]) -> [DMESG-FAIL][96] ([fdo#108145] / [i915#95])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl4/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl6/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
- shard-kbl: [DMESG-FAIL][97] ([i915#95]) -> [FAIL][98] ([i915#265])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl4/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl7/igt@[email protected]

* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: [DMESG-WARN][99] ([i915#93] / [i915#95]) -> [DMESG-WARN][100] ([i915#180]) +2 similar issues
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8641/shard-kbl2/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/shard-kbl1/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#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1149]: https://gitlab.freedesktop.org/drm/intel/issues/1149
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1820]: https://gitlab.freedesktop.org/drm/intel/issues/1820
[i915#1899]: https://gitlab.freedesktop.org/drm/intel/issues/1899
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#42]: https://gitlab.freedesktop.org/drm/intel/issues/42
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456
[i915#468]: https://gitlab.freedesktop.org/drm/intel/issues/468
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133

Participating hosts (11 -> 8)
------------------------------

Missing (3): pig-skl-6260u pig-glk-j5005 pig-icl-1065g7

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

* CI: CI-20190529 -> None
* IGT: IGT_5712 -> IGTPW_4683
* Piglit: piglit_4509 -> None

CI-20190529: 20190529
CI_DRM_8641: aac91f91c7be78f53b352237d968dfa1996b2d4b @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4683: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4683/index.html
IGT_5712: eba1135ddd35f9d3097ed91032aefe8f9a9f9d02 @ 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_4683/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#9 lore raw

[igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t,1/2] runner: Inject a message when killing test to taints

In reply to Petri Latvala
== Series Details ==

== Series Details ==

Series: series starting with [i-g-t,1/2] runner: Inject a message when killing test to taints
URL : https://patchwork.freedesktop.org/series/78526/
State : warning

== Summary ==

Did not get list of undocumented tests for this run, something is wrong!

Other than that, pipeline status: FAILED.

see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/162930 for the overview.

build-containers:build-debian-armhf has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/3171590):
Using docker image sha256:594aa868d31ee3304dee8cae8a3433c89a6fcfcf6c7d420c04cce22f60147176 for registry.freedesktop.org/wayland/ci-templates/buildah:2019-08-13.0 ... section_end:1592483963:prepare_executor
section_start:1592483963:prepare_script
Preparing environment
Running on runner-j4Lrg1oF-project-3185-concurrent-1 via gst-htz-1...
section_end:1592483965:prepare_script
section_start:1592483965:get_sources
Getting source from Git repository
Fetching changes...
Initialized empty Git repository in /builds/gfx-ci/igt-ci-tags/.git/
Created fresh repository.
warning: redirecting to https://gitlab-ci-hetzner.freedesktop.org/gfx-ci/igt-ci-tags.git/
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
fatal: the remote end hung up unexpectedly
section_end:1592484027:get_sources
section_start:1592484027:upload_artifacts_on_failure
Uploading artifacts for failed job
section_end:1592484029:upload_artifacts_on_failure
ERROR: Job failed: exit code 1

== Logs ==

For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/162930
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev