All of lore.kernel.org
 help / color / mirror / Atom feed
* [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder
@ 2020-01-22 16:43 Ville Syrjala
  2020-01-22 17:09 ` Chris Wilson
                   ` (3 more replies)
  0 siblings, 4 replies; 7+ messages in thread
From: Ville Syrjala @ 2020-01-22 16:43 UTC (permalink / raw)
  To: igt-dev

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

The current gdb detection only works for the parent igt process,
but none of its children will see the gdb and so won't trap properly
in igt_fail_assert(). Also we will not detect gdb if it was attached
after the fact. Fix all of that by looking for the "TracerPid"
information in /proc/<pid>/status. We'll leave the current "assume
parent may be gdb" approach as a fallback.

Also annoyingly by default gdb will only track a single process.
To make it track all of them, and let them all run simultanously
one needs the following incantations:
 set detach-on-fork off
 set schedule-multiple on

Maybe that will save someone from having to trawl as many
docs/gogole hits as I did.

Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
 lib/igt_core.c | 38 ++++++++++++++++++++++++++++++++++++--
 1 file changed, 36 insertions(+), 2 deletions(-)

diff --git a/lib/igt_core.c b/lib/igt_core.c
index 0a0068946a6a..109b5926eac4 100644
--- a/lib/igt_core.c
+++ b/lib/igt_core.c
@@ -1609,12 +1609,12 @@ void igt_describe_f(const char *fmt, ...)
 	assert(ret < sizeof(__current_description));
 }
 
-static bool running_under_gdb(void)
+static bool is_gdb(pid_t pid)
 {
 	char pathname[30], buf[1024];
 	ssize_t len;
 
-	sprintf(pathname, "/proc/%d/exe", getppid());
+	sprintf(pathname, "/proc/%d/exe", pid);
 	len = readlink(pathname, buf, sizeof(buf) - 1);
 	if (len < 0)
 		return false;
@@ -1624,6 +1624,40 @@ static bool running_under_gdb(void)
 	return strncmp(basename(buf), "gdb", 3) == 0;
 }
 
+static pid_t tracer_pid(void)
+{
+	char pathname[30];
+	pid_t pid = 0;
+	FILE *f;
+
+	sprintf(pathname, "/proc/%d/status", getpid());
+
+	f = fopen(pathname, "r");
+	if (!f)
+		return getppid();
+
+	for (;;) {
+		char buf[1024];
+		char *s;
+
+		s = fgets(buf, sizeof(buf), f);
+		if (!s)
+			break;
+
+		if (sscanf(s, "TracerPid: %d", &pid) == 1)
+			break;
+	}
+
+	fclose(f);
+
+	return pid ?: getppid();
+}
+
+static bool running_under_gdb(void)
+{
+	return is_gdb(tracer_pid());
+}
+
 static void __write_stderr(const char *str, size_t len)
 {
 	igt_ignore_warn(write(STDERR_FILENO, str, len));
-- 
2.24.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply related	[flat|nested] 7+ messages in thread

* Re: [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder
  2020-01-22 16:43 [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder Ville Syrjala
@ 2020-01-22 17:09 ` Chris Wilson
  2020-01-22 17:21   ` Ville Syrjälä
  2020-01-22 19:56 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
                   ` (2 subsequent siblings)
  3 siblings, 1 reply; 7+ messages in thread
From: Chris Wilson @ 2020-01-22 17:09 UTC (permalink / raw)
  To: Ville Syrjala, igt-dev

Quoting Ville Syrjala (2020-01-22 16:43:32)
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> The current gdb detection only works for the parent igt process,
> but none of its children will see the gdb and so won't trap properly
> in igt_fail_assert(). Also we will not detect gdb if it was attached
> after the fact. Fix all of that by looking for the "TracerPid"
> information in /proc/<pid>/status. We'll leave the current "assume
> parent may be gdb" approach as a fallback.
> 
> Also annoyingly by default gdb will only track a single process.
> To make it track all of them, and let them all run simultanously
> one needs the following incantations:
>  set detach-on-fork off
>  set schedule-multiple on
> 
> Maybe that will save someone from having to trawl as many
> docs/gogole hits as I did.
> 
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  lib/igt_core.c | 38 ++++++++++++++++++++++++++++++++++++--
>  1 file changed, 36 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/igt_core.c b/lib/igt_core.c
> index 0a0068946a6a..109b5926eac4 100644
> --- a/lib/igt_core.c
> +++ b/lib/igt_core.c
> @@ -1609,12 +1609,12 @@ void igt_describe_f(const char *fmt, ...)
>         assert(ret < sizeof(__current_description));
>  }
>  
> -static bool running_under_gdb(void)
> +static bool is_gdb(pid_t pid)
>  {
>         char pathname[30], buf[1024];
>         ssize_t len;
>  
> -       sprintf(pathname, "/proc/%d/exe", getppid());
> +       sprintf(pathname, "/proc/%d/exe", pid);
>         len = readlink(pathname, buf, sizeof(buf) - 1);
>         if (len < 0)
>                 return false;
> @@ -1624,6 +1624,40 @@ static bool running_under_gdb(void)
>         return strncmp(basename(buf), "gdb", 3) == 0;
>  }
>  
> +static pid_t tracer_pid(void)
> +{
> +       char pathname[30];
> +       pid_t pid = 0;
> +       FILE *f;
> +
> +       sprintf(pathname, "/proc/%d/status", getpid());
> +
> +       f = fopen(pathname, "r");
> +       if (!f)
> +               return getppid();
> +
> +       for (;;) {
> +               char buf[1024];
> +               char *s;
> +
> +               s = fgets(buf, sizeof(buf), f);

I'd prefer fgetline, /proc/<pid>status is >1024 bytes so there's always
that chance we cut the TracerPid line.

> +               if (!s)
> +                       break;
> +
> +               if (sscanf(s, "TracerPid: %d", &pid) == 1)
> +                       break;
> +       }
> +
> +       fclose(f);
> +
> +       return pid ?: getppid();

Makes sense.

> +}
> +
> +static bool running_under_gdb(void)
> +{

/*
 * Annoyingly by default gdb will only track a single process.
 * To make it track all of them, and let them all run simultaneously
 * one needs the following incantations:
 *   set detach-on-fork off
 *   set schedule-multiple on
 */


TIL two things, so
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder
  2020-01-22 17:09 ` Chris Wilson
@ 2020-01-22 17:21   ` Ville Syrjälä
  2020-01-22 17:31     ` Chris Wilson
  0 siblings, 1 reply; 7+ messages in thread
From: Ville Syrjälä @ 2020-01-22 17:21 UTC (permalink / raw)
  To: Chris Wilson; +Cc: igt-dev

On Wed, Jan 22, 2020 at 05:09:19PM +0000, Chris Wilson wrote:
> Quoting Ville Syrjala (2020-01-22 16:43:32)
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > The current gdb detection only works for the parent igt process,
> > but none of its children will see the gdb and so won't trap properly
> > in igt_fail_assert(). Also we will not detect gdb if it was attached
> > after the fact. Fix all of that by looking for the "TracerPid"
> > information in /proc/<pid>/status. We'll leave the current "assume
> > parent may be gdb" approach as a fallback.
> > 
> > Also annoyingly by default gdb will only track a single process.
> > To make it track all of them, and let them all run simultanously
> > one needs the following incantations:
> >  set detach-on-fork off
> >  set schedule-multiple on
> > 
> > Maybe that will save someone from having to trawl as many
> > docs/gogole hits as I did.
> > 
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> >  lib/igt_core.c | 38 ++++++++++++++++++++++++++++++++++++--
> >  1 file changed, 36 insertions(+), 2 deletions(-)
> > 
> > diff --git a/lib/igt_core.c b/lib/igt_core.c
> > index 0a0068946a6a..109b5926eac4 100644
> > --- a/lib/igt_core.c
> > +++ b/lib/igt_core.c
> > @@ -1609,12 +1609,12 @@ void igt_describe_f(const char *fmt, ...)
> >         assert(ret < sizeof(__current_description));
> >  }
> >  
> > -static bool running_under_gdb(void)
> > +static bool is_gdb(pid_t pid)
> >  {
> >         char pathname[30], buf[1024];
> >         ssize_t len;
> >  
> > -       sprintf(pathname, "/proc/%d/exe", getppid());
> > +       sprintf(pathname, "/proc/%d/exe", pid);
> >         len = readlink(pathname, buf, sizeof(buf) - 1);
> >         if (len < 0)
> >                 return false;
> > @@ -1624,6 +1624,40 @@ static bool running_under_gdb(void)
> >         return strncmp(basename(buf), "gdb", 3) == 0;
> >  }
> >  
> > +static pid_t tracer_pid(void)
> > +{
> > +       char pathname[30];
> > +       pid_t pid = 0;
> > +       FILE *f;
> > +
> > +       sprintf(pathname, "/proc/%d/status", getpid());
> > +
> > +       f = fopen(pathname, "r");
> > +       if (!f)
> > +               return getppid();
> > +
> > +       for (;;) {
> > +               char buf[1024];
> > +               char *s;
> > +
> > +               s = fgets(buf, sizeof(buf), f);
> 
> I'd prefer fgetline, /proc/<pid>status is >1024 bytes so there's always
> that chance we cut the TracerPid line.

fgets() reads at most one line (which means my 1024 copypasta is
probably a bit much). Not sure what fgetline() is.

> 
> > +               if (!s)
> > +                       break;
> > +
> > +               if (sscanf(s, "TracerPid: %d", &pid) == 1)
> > +                       break;
> > +       }
> > +
> > +       fclose(f);
> > +
> > +       return pid ?: getppid();
> 
> Makes sense.
> 
> > +}
> > +
> > +static bool running_under_gdb(void)
> > +{
> 
> /*
>  * Annoyingly by default gdb will only track a single process.
>  * To make it track all of them, and let them all run simultaneously
>  * one needs the following incantations:
>  *   set detach-on-fork off
>  *   set schedule-multiple on
>  */

Yeah, a comment is probably a good idea for this.

> 
> 
> TIL two things, so
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris

-- 
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder
  2020-01-22 17:21   ` Ville Syrjälä
@ 2020-01-22 17:31     ` Chris Wilson
  0 siblings, 0 replies; 7+ messages in thread
From: Chris Wilson @ 2020-01-22 17:31 UTC (permalink / raw)
  To: Ville Syrjälä; +Cc: igt-dev

Quoting Ville Syrjälä (2020-01-22 17:21:26)
> On Wed, Jan 22, 2020 at 05:09:19PM +0000, Chris Wilson wrote:
> > Quoting Ville Syrjala (2020-01-22 16:43:32)
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > 
> > > The current gdb detection only works for the parent igt process,
> > > but none of its children will see the gdb and so won't trap properly
> > > in igt_fail_assert(). Also we will not detect gdb if it was attached
> > > after the fact. Fix all of that by looking for the "TracerPid"
> > > information in /proc/<pid>/status. We'll leave the current "assume
> > > parent may be gdb" approach as a fallback.
> > > 
> > > Also annoyingly by default gdb will only track a single process.
> > > To make it track all of them, and let them all run simultanously
> > > one needs the following incantations:
> > >  set detach-on-fork off
> > >  set schedule-multiple on
> > > 
> > > Maybe that will save someone from having to trawl as many
> > > docs/gogole hits as I did.
> > > 
> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > ---
> > >  lib/igt_core.c | 38 ++++++++++++++++++++++++++++++++++++--
> > >  1 file changed, 36 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/lib/igt_core.c b/lib/igt_core.c
> > > index 0a0068946a6a..109b5926eac4 100644
> > > --- a/lib/igt_core.c
> > > +++ b/lib/igt_core.c
> > > @@ -1609,12 +1609,12 @@ void igt_describe_f(const char *fmt, ...)
> > >         assert(ret < sizeof(__current_description));
> > >  }
> > >  
> > > -static bool running_under_gdb(void)
> > > +static bool is_gdb(pid_t pid)
> > >  {
> > >         char pathname[30], buf[1024];
> > >         ssize_t len;
> > >  
> > > -       sprintf(pathname, "/proc/%d/exe", getppid());
> > > +       sprintf(pathname, "/proc/%d/exe", pid);
> > >         len = readlink(pathname, buf, sizeof(buf) - 1);
> > >         if (len < 0)
> > >                 return false;
> > > @@ -1624,6 +1624,40 @@ static bool running_under_gdb(void)
> > >         return strncmp(basename(buf), "gdb", 3) == 0;
> > >  }
> > >  
> > > +static pid_t tracer_pid(void)
> > > +{
> > > +       char pathname[30];
> > > +       pid_t pid = 0;
> > > +       FILE *f;
> > > +
> > > +       sprintf(pathname, "/proc/%d/status", getpid());
> > > +
> > > +       f = fopen(pathname, "r");
> > > +       if (!f)
> > > +               return getppid();
> > > +
> > > +       for (;;) {
> > > +               char buf[1024];
> > > +               char *s;
> > > +
> > > +               s = fgets(buf, sizeof(buf), f);
> > 
> > I'd prefer fgetline, /proc/<pid>status is >1024 bytes so there's always
> > that chance we cut the TracerPid line.
> 
> fgets() reads at most one line (which means my 1024 copypasta is
> probably a bit much). Not sure what fgetline() is.

I meant getline. fgets breaks on newlines as well? man says it does,
fair enough. I'd make that 3 things, but I'm going to forget at least
two of them by tomorrow.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_core: Detect gdb harder
  2020-01-22 16:43 [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder Ville Syrjala
  2020-01-22 17:09 ` Chris Wilson
@ 2020-01-22 19:56 ` Patchwork
  2020-01-23 13:51 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
  2020-01-23 22:59 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
  3 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2020-01-22 19:56 UTC (permalink / raw)
  To: Ville Syrjälä; +Cc: igt-dev

== Series Details ==

Series: lib/igt_core: Detect gdb harder
URL   : https://patchwork.freedesktop.org/series/72413/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_7796 -> IGTPW_3970
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

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

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

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

### IGT changes ###

#### Issues hit ####

  * igt@fbdev@mmap:
    - fi-icl-dsi:         [PASS][1] -> [DMESG-WARN][2] ([i915#109])
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-icl-dsi/igt@fbdev@mmap.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-icl-dsi/igt@fbdev@mmap.html

  * igt@gem_close_race@basic-threads:
    - fi-byt-j1900:       [PASS][3] -> [INCOMPLETE][4] ([i915#45])
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-byt-j1900/igt@gem_close_race@basic-threads.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-byt-j1900/igt@gem_close_race@basic-threads.html

  * igt@gem_exec_suspend@basic-s3:
    - fi-cml-s:           [PASS][5] -> [INCOMPLETE][6] ([i915#283])
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-cml-s/igt@gem_exec_suspend@basic-s3.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-cml-s/igt@gem_exec_suspend@basic-s3.html

  * igt@i915_selftest@live_blt:
    - fi-ivb-3770:        [PASS][7] -> [DMESG-FAIL][8] ([i915#770])
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-ivb-3770/igt@i915_selftest@live_blt.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-ivb-3770/igt@i915_selftest@live_blt.html

  * igt@i915_selftest@live_coherency:
    - fi-cfl-guc:         [PASS][9] -> [DMESG-FAIL][10] ([i915#889]) +7 similar issues
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-cfl-guc/igt@i915_selftest@live_coherency.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-cfl-guc/igt@i915_selftest@live_coherency.html

  * igt@i915_selftest@live_gt_timelines:
    - fi-cfl-guc:         [PASS][11] -> [DMESG-WARN][12] ([i915#889]) +23 similar issues
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-cfl-guc/igt@i915_selftest@live_gt_timelines.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-cfl-guc/igt@i915_selftest@live_gt_timelines.html

  * igt@kms_chamelium@hdmi-hpd-fast:
    - fi-kbl-7500u:       [PASS][13] -> [FAIL][14] ([fdo#111096] / [i915#323])
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html

  
#### Possible fixes ####

  * igt@gem_exec_suspend@basic-s0:
    - fi-cml-s:           [FAIL][15] ([fdo#103375]) -> [PASS][16]
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-cml-s/igt@gem_exec_suspend@basic-s0.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-cml-s/igt@gem_exec_suspend@basic-s0.html

  * igt@i915_selftest@live_gem_contexts:
    - fi-cfl-8700k:       [INCOMPLETE][17] ([CI#80] / [i915#424]) -> [PASS][18]
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-cfl-8700k/igt@i915_selftest@live_gem_contexts.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-cfl-8700k/igt@i915_selftest@live_gem_contexts.html

  
#### Warnings ####

  * igt@gem_exec_parallel@contexts:
    - fi-byt-n2820:       [FAIL][19] -> [TIMEOUT][20] ([fdo#112271])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-byt-n2820/igt@gem_exec_parallel@contexts.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-byt-n2820/igt@gem_exec_parallel@contexts.html

  * igt@gem_exec_parallel@fds:
    - fi-byt-n2820:       [INCOMPLETE][21] ([i915#45]) -> [TIMEOUT][22] ([fdo#112271])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-byt-n2820/igt@gem_exec_parallel@fds.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-byt-n2820/igt@gem_exec_parallel@fds.html

  * igt@i915_selftest@live_blt:
    - fi-hsw-4770r:       [DMESG-FAIL][23] ([i915#553] / [i915#725]) -> [DMESG-FAIL][24] ([i915#725])
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/fi-hsw-4770r/igt@i915_selftest@live_blt.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/fi-hsw-4770r/igt@i915_selftest@live_blt.html

  
  [CI#80]: https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/80
  [fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
  [fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
  [fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271
  [i915#109]: https://gitlab.freedesktop.org/drm/intel/issues/109
  [i915#283]: https://gitlab.freedesktop.org/drm/intel/issues/283
  [i915#323]: https://gitlab.freedesktop.org/drm/intel/issues/323
  [i915#424]: https://gitlab.freedesktop.org/drm/intel/issues/424
  [i915#45]: https://gitlab.freedesktop.org/drm/intel/issues/45
  [i915#553]: https://gitlab.freedesktop.org/drm/intel/issues/553
  [i915#725]: https://gitlab.freedesktop.org/drm/intel/issues/725
  [i915#770]: https://gitlab.freedesktop.org/drm/intel/issues/770
  [i915#889]: https://gitlab.freedesktop.org/drm/intel/issues/889


Participating hosts (49 -> 47)
------------------------------

  Additional (4): fi-kbl-7560u fi-kbl-r fi-ilk-650 fi-elk-e7500 
  Missing    (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-bdw-samus 


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

  * CI: CI-20190529 -> None
  * IGT: IGT_5377 -> IGTPW_3970

  CI-20190529: 20190529
  CI_DRM_7796: 2d96f6aa93defd19024f701d05c0284034e914e2 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_3970: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/index.html
  IGT_5377: 1e6cb3e75925cf623df04f78430ae9299632ec3f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [igt-dev] ✗ GitLab.Pipeline: warning for lib/igt_core: Detect gdb harder
  2020-01-22 16:43 [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder Ville Syrjala
  2020-01-22 17:09 ` Chris Wilson
  2020-01-22 19:56 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
@ 2020-01-23 13:51 ` Patchwork
  2020-01-23 22:59 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
  3 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2020-01-23 13:51 UTC (permalink / raw)
  To: Ville Syrjälä; +Cc: igt-dev

== Series Details ==

Series: lib/igt_core: Detect gdb harder
URL   : https://patchwork.freedesktop.org/series/72413/
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/100065 for the overview.

test:ninja-test-arm64 has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/1427577):
    [test_root]           Directory that contains the IGT tests. The environment
                          variable IGT_TEST_ROOT will be used if set, overriding
                          this option if given.
  Cannot open /builds/gfx-ci/igt-ci-tags/build/tmpdirZyMyQ0/test-list.txt
  -------
  
  Full log written to /builds/gfx-ci/igt-ci-tags/build/meson-logs/testlog.txt
  FAILED: meson-test 
  /usr/bin/meson test --no-rebuild --print-errorlogs
  ninja: build stopped: subcommand failed.
  section_end:1579721465:build_script
  ^[[0Ksection_start:1579721465:after_script
  ^[[0Ksection_end:1579721466:after_script
  ^[[0Ksection_start:1579721466:upload_artifacts_on_failure
  ^[[0K^[[32;1mUploading artifacts...^[[0;m
  build: found 1375 matching files                  ^[[0;m 
  Uploading artifacts to coordinator... ok          ^[[0;m  id^[[0;m=1427577 responseStatus^[[0;m=201 Created token^[[0;m=fneLt31V
  section_end:1579721473:upload_artifacts_on_failure
  ^[[0K^[[31;1mERROR: Job failed: exit code 1
  ^[[0;m

test:ninja-test-arm64 has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/1427843):
    [test_root]           Directory that contains the IGT tests. The environment
                          variable IGT_TEST_ROOT will be used if set, overriding
                          this option if given.
  Cannot open /builds/gfx-ci/igt-ci-tags/build/tmpdirnQLZds/test-list.txt
  -------
  
  Full log written to /builds/gfx-ci/igt-ci-tags/build/meson-logs/testlog.txt
  FAILED: meson-test 
  /usr/bin/meson test --no-rebuild --print-errorlogs
  ninja: build stopped: subcommand failed.
  section_end:1579721835:build_script
  ^[[0Ksection_start:1579721835:after_script
  ^[[0Ksection_end:1579721837:after_script
  ^[[0Ksection_start:1579721837:upload_artifacts_on_failure
  ^[[0K^[[32;1mUploading artifacts...^[[0;m
  build: found 1375 matching files                  ^[[0;m 
  Uploading artifacts to coordinator... ok          ^[[0;m  id^[[0;m=1427843 responseStatus^[[0;m=201 Created token^[[0;m=sqjQ_yZh
  section_end:1579721843:upload_artifacts_on_failure
  ^[[0K^[[31;1mERROR: Job failed: exit code 1
  ^[[0;m

test:ninja-test-arm64 has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/1427948):
    [test_root]           Directory that contains the IGT tests. The environment
                          variable IGT_TEST_ROOT will be used if set, overriding
                          this option if given.
  Cannot open /builds/gfx-ci/igt-ci-tags/build/tmpdirzZL88m/test-list.txt
  -------
  
  Full log written to /builds/gfx-ci/igt-ci-tags/build/meson-logs/testlog.txt
  FAILED: meson-test 
  /usr/bin/meson test --no-rebuild --print-errorlogs
  ninja: build stopped: subcommand failed.
  section_end:1579722222:build_script
  ^[[0Ksection_start:1579722222:after_script
  ^[[0Ksection_end:1579722224:after_script
  ^[[0Ksection_start:1579722224:upload_artifacts_on_failure
  ^[[0K^[[32;1mUploading artifacts...^[[0;m
  build: found 1375 matching files                  ^[[0;m 
  Uploading artifacts to coordinator... ok          ^[[0;m  id^[[0;m=1427948 responseStatus^[[0;m=201 Created token^[[0;m=ByXFs1ez
  section_end:1579722230:upload_artifacts_on_failure
  ^[[0K^[[31;1mERROR: Job failed: exit code 1
  ^[[0;m

== Logs ==

For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/100065
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [igt-dev] ✓ Fi.CI.IGT: success for lib/igt_core: Detect gdb harder
  2020-01-22 16:43 [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder Ville Syrjala
                   ` (2 preceding siblings ...)
  2020-01-23 13:51 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
@ 2020-01-23 22:59 ` Patchwork
  3 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2020-01-23 22:59 UTC (permalink / raw)
  To: Ville Syrjälä; +Cc: igt-dev

== Series Details ==

Series: lib/igt_core: Detect gdb harder
URL   : https://patchwork.freedesktop.org/series/72413/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_7796_full -> IGTPW_3970_full
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

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

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

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

### IGT changes ###

#### Issues hit ####

  * igt@gem_ctx_isolation@vcs1-dirty-create:
    - shard-iclb:         [PASS][1] -> [SKIP][2] ([fdo#109276] / [fdo#112080]) +2 similar issues
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb4/igt@gem_ctx_isolation@vcs1-dirty-create.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb3/igt@gem_ctx_isolation@vcs1-dirty-create.html

  * igt@gem_ctx_persistence@rcs0-mixed-process:
    - shard-tglb:         [PASS][3] -> [FAIL][4] ([i915#679])
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-tglb7/igt@gem_ctx_persistence@rcs0-mixed-process.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-tglb7/igt@gem_ctx_persistence@rcs0-mixed-process.html

  * igt@gem_exec_schedule@independent-bsd2:
    - shard-iclb:         [PASS][5] -> [SKIP][6] ([fdo#109276]) +12 similar issues
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb2/igt@gem_exec_schedule@independent-bsd2.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb3/igt@gem_exec_schedule@independent-bsd2.html

  * igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd:
    - shard-iclb:         [PASS][7] -> [SKIP][8] ([fdo#112146]) +4 similar issues
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb7/igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb2/igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd.html

  * igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing:
    - shard-kbl:          [PASS][9] -> [INCOMPLETE][10] ([fdo#103665] / [i915#970])
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-kbl2/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-kbl6/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html

  * igt@gem_persistent_relocs@forked-interruptible-thrash-inactive:
    - shard-hsw:          [PASS][11] -> [INCOMPLETE][12] ([i915#61])
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-hsw5/igt@gem_persistent_relocs@forked-interruptible-thrash-inactive.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-hsw7/igt@gem_persistent_relocs@forked-interruptible-thrash-inactive.html

  * igt@gem_userptr_blits@sync-unmap-after-close:
    - shard-snb:          [PASS][13] -> [DMESG-WARN][14] ([fdo#111870] / [i915#478]) +1 similar issue
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-snb1/igt@gem_userptr_blits@sync-unmap-after-close.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-snb2/igt@gem_userptr_blits@sync-unmap-after-close.html

  * igt@i915_selftest@mock_requests:
    - shard-tglb:         [PASS][15] -> [INCOMPLETE][16] ([i915#472]) +1 similar issue
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-tglb1/igt@i915_selftest@mock_requests.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-tglb2/igt@i915_selftest@mock_requests.html
    - shard-apl:          [PASS][17] -> [INCOMPLETE][18] ([fdo#103927])
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-apl2/igt@i915_selftest@mock_requests.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-apl7/igt@i915_selftest@mock_requests.html
    - shard-kbl:          [PASS][19] -> [INCOMPLETE][20] ([fdo#103665])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-kbl2/igt@i915_selftest@mock_requests.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-kbl4/igt@i915_selftest@mock_requests.html

  * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt:
    - shard-kbl:          [PASS][21] -> [FAIL][22] ([i915#49])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-kbl3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html
    - shard-glk:          [PASS][23] -> [FAIL][24] ([i915#49])
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-glk4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-glk9/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html

  * igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary:
    - shard-apl:          [PASS][25] -> [FAIL][26] ([i915#49])
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-apl7/igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-apl6/igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary.html

  * igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
    - shard-apl:          [PASS][27] -> [DMESG-WARN][28] ([i915#180]) +2 similar issues
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-apl7/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-apl7/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html

  * igt@kms_psr@psr2_cursor_mmap_cpu:
    - shard-iclb:         [PASS][29] -> [SKIP][30] ([fdo#109441]) +1 similar issue
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb1/igt@kms_psr@psr2_cursor_mmap_cpu.html

  * igt@kms_vblank@pipe-a-ts-continuation-suspend:
    - shard-kbl:          [PASS][31] -> [DMESG-WARN][32] ([i915#180]) +8 similar issues
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-kbl1/igt@kms_vblank@pipe-a-ts-continuation-suspend.html

  * igt@perf_pmu@busy-vcs1:
    - shard-iclb:         [PASS][33] -> [SKIP][34] ([fdo#112080]) +13 similar issues
   [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb2/igt@perf_pmu@busy-vcs1.html
   [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb3/igt@perf_pmu@busy-vcs1.html

  
#### Possible fixes ####

  * igt@gem_ctx_persistence@vcs1-queued:
    - shard-iclb:         [SKIP][35] ([fdo#109276] / [fdo#112080]) -> [PASS][36] +4 similar issues
   [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb6/igt@gem_ctx_persistence@vcs1-queued.html
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb2/igt@gem_ctx_persistence@vcs1-queued.html

  * igt@gem_exec_schedule@deep-bsd:
    - shard-iclb:         [SKIP][37] ([fdo#112146]) -> [PASS][38] +3 similar issues
   [37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb4/igt@gem_exec_schedule@deep-bsd.html
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb3/igt@gem_exec_schedule@deep-bsd.html

  * igt@gem_exec_store@cachelines-vcs1:
    - shard-iclb:         [SKIP][39] ([fdo#112080]) -> [PASS][40] +4 similar issues
   [39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb6/igt@gem_exec_store@cachelines-vcs1.html
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb4/igt@gem_exec_store@cachelines-vcs1.html

  * igt@gem_mmap_gtt@basic-small-bo-tiledy:
    - shard-snb:          [DMESG-WARN][41] ([i915#478]) -> [PASS][42] +1 similar issue
   [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-snb2/igt@gem_mmap_gtt@basic-small-bo-tiledy.html
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-snb1/igt@gem_mmap_gtt@basic-small-bo-tiledy.html

  * igt@gem_persistent_relocs@forked-faulting-reloc-thrashing:
    - shard-kbl:          [INCOMPLETE][43] ([fdo#103665]) -> [PASS][44]
   [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-kbl3/igt@gem_persistent_relocs@forked-faulting-reloc-thrashing.html
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-kbl7/igt@gem_persistent_relocs@forked-faulting-reloc-thrashing.html

  * igt@gem_persistent_relocs@forked-interruptible-thrashing:
    - shard-apl:          [INCOMPLETE][45] ([fdo#103927]) -> [PASS][46]
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-apl1/igt@gem_persistent_relocs@forked-interruptible-thrashing.html
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-apl1/igt@gem_persistent_relocs@forked-interruptible-thrashing.html

  * igt@gem_persistent_relocs@forked-thrash-inactive:
    - shard-hsw:          [INCOMPLETE][47] ([i915#61]) -> [PASS][48] +2 similar issues
   [47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-hsw7/igt@gem_persistent_relocs@forked-thrash-inactive.html
   [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-hsw2/igt@gem_persistent_relocs@forked-thrash-inactive.html

  * igt@gem_ppgtt@flink-and-close-vma-leak:
    - shard-glk:          [FAIL][49] ([i915#644]) -> [PASS][50]
   [49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-glk8/igt@gem_ppgtt@flink-and-close-vma-leak.html
   [50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-glk5/igt@gem_ppgtt@flink-and-close-vma-leak.html
    - shard-apl:          [FAIL][51] ([i915#644]) -> [PASS][52]
   [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-apl1/igt@gem_ppgtt@flink-and-close-vma-leak.html
   [52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-apl8/igt@gem_ppgtt@flink-and-close-vma-leak.html

  * igt@gem_userptr_blits@map-fixed-invalidate-busy:
    - shard-snb:          [DMESG-WARN][53] ([fdo#111870] / [i915#478]) -> [PASS][54]
   [53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-snb6/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
   [54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-snb1/igt@gem_userptr_blits@map-fixed-invalidate-busy.html

  * igt@gem_workarounds@suspend-resume-context:
    - shard-apl:          [DMESG-WARN][55] ([i915#180]) -> [PASS][56]
   [55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-apl6/igt@gem_workarounds@suspend-resume-context.html
   [56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-apl2/igt@gem_workarounds@suspend-resume-context.html

  * igt@gen7_exec_parse@basic-allocation:
    - shard-hsw:          [FAIL][57] ([i915#694]) -> [PASS][58] +1 similar issue
   [57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-hsw2/igt@gen7_exec_parse@basic-allocation.html
   [58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-hsw5/igt@gen7_exec_parse@basic-allocation.html

  * igt@i915_pm_dc@dc5-dpms:
    - shard-iclb:         [FAIL][59] ([i915#447]) -> [PASS][60]
   [59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb3/igt@i915_pm_dc@dc5-dpms.html
   [60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb8/igt@i915_pm_dc@dc5-dpms.html

  * igt@i915_pm_dc@dc6-dpms:
    - shard-iclb:         [FAIL][61] ([i915#454]) -> [PASS][62] +1 similar issue
   [61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb3/igt@i915_pm_dc@dc6-dpms.html
   [62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb1/igt@i915_pm_dc@dc6-dpms.html

  * igt@i915_selftest@mock_requests:
    - shard-glk:          [INCOMPLETE][63] ([i915#58] / [k.org#198133]) -> [PASS][64]
   [63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-glk6/igt@i915_selftest@mock_requests.html
   [64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-glk1/igt@i915_selftest@mock_requests.html

  * igt@i915_suspend@debugfs-reader:
    - shard-kbl:          [DMESG-WARN][65] ([i915#180]) -> [PASS][66] +2 similar issues
   [65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-kbl2/igt@i915_suspend@debugfs-reader.html
   [66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-kbl2/igt@i915_suspend@debugfs-reader.html

  * igt@kms_fbcon_fbt@psr-suspend:
    - shard-iclb:         [INCOMPLETE][67] ([i915#140]) -> [PASS][68]
   [67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb3/igt@kms_fbcon_fbt@psr-suspend.html
   [68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb6/igt@kms_fbcon_fbt@psr-suspend.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-mmap-gtt:
    - shard-tglb:         [FAIL][69] ([i915#49]) -> [PASS][70] +3 similar issues
   [69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-tglb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-mmap-gtt.html
   [70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-mmap-gtt.html

  * igt@kms_psr@psr2_cursor_blt:
    - shard-iclb:         [SKIP][71] ([fdo#109441]) -> [PASS][72] +1 similar issue
   [71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb4/igt@kms_psr@psr2_cursor_blt.html
   [72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html

  * igt@kms_setmode@basic:
    - shard-apl:          [FAIL][73] ([i915#31]) -> [PASS][74]
   [73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-apl3/igt@kms_setmode@basic.html
   [74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-apl1/igt@kms_setmode@basic.html

  * igt@prime_vgem@fence-wait-bsd2:
    - shard-iclb:         [SKIP][75] ([fdo#109276]) -> [PASS][76] +14 similar issues
   [75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb8/igt@prime_vgem@fence-wait-bsd2.html
   [76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb4/igt@prime_vgem@fence-wait-bsd2.html

  
#### Warnings ####

  * igt@gem_ctx_isolation@vcs1-nonpriv-switch:
    - shard-iclb:         [FAIL][77] ([IGT#28]) -> [SKIP][78] ([fdo#109276] / [fdo#112080])
   [77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-iclb2/igt@gem_ctx_isolation@vcs1-nonpriv-switch.html
   [78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-iclb5/igt@gem_ctx_isolation@vcs1-nonpriv-switch.html

  * igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing:
    - shard-hsw:          [INCOMPLETE][79] ([i915#530] / [i915#61]) -> [INCOMPLETE][80] ([i915#61])
   [79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-hsw2/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html
   [80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-hsw7/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html

  * igt@gem_tiled_blits@normal:
    - shard-hsw:          [FAIL][81] ([i915#694]) -> [FAIL][82] ([i915#818])
   [81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7796/shard-hsw2/igt@gem_tiled_blits@normal.html
   [82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/shard-hsw1/igt@gem_tiled_blits@normal.html

  
  [IGT#28]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/28
  [fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
  [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
  [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
  [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
  [fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
  [fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
  [fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
  [i915#140]: https://gitlab.freedesktop.org/drm/intel/issues/140
  [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
  [i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
  [i915#447]: https://gitlab.freedesktop.org/drm/intel/issues/447
  [i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
  [i915#472]: https://gitlab.freedesktop.org/drm/intel/issues/472
  [i915#478]: https://gitlab.freedesktop.org/drm/intel/issues/478
  [i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
  [i915#530]: https://gitlab.freedesktop.org/drm/intel/issues/530
  [i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
  [i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61
  [i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644
  [i915#679]: https://gitlab.freedesktop.org/drm/intel/issues/679
  [i915#694]: https://gitlab.freedesktop.org/drm/intel/issues/694
  [i915#818]: https://gitlab.freedesktop.org/drm/intel/issues/818
  [i915#970]: https://gitlab.freedesktop.org/drm/intel/issues/970
  [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133


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

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


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

  * CI: CI-20190529 -> None
  * IGT: IGT_5377 -> IGTPW_3970
  * Piglit: piglit_4509 -> None

  CI-20190529: 20190529
  CI_DRM_7796: 2d96f6aa93defd19024f701d05c0284034e914e2 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_3970: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3970/index.html
  IGT_5377: 1e6cb3e75925cf623df04f78430ae9299632ec3f @ 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_3970/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2020-01-23 22:59 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-22 16:43 [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder Ville Syrjala
2020-01-22 17:09 ` Chris Wilson
2020-01-22 17:21   ` Ville Syrjälä
2020-01-22 17:31     ` Chris Wilson
2020-01-22 19:56 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-23 13:51 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2020-01-23 22:59 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.