public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for tests/gem_shrink: Exercise OOM and other routes to shrinking in reasonable time (rev2)
Date: Mon, 07 Jan 2019 18:00:35 -0000	[thread overview]
Message-ID: <20190107180035.25009.4910@emeril.freedesktop.org> (raw)
In-Reply-To: <20190104153709.19350-1-tvrtko.ursulin@linux.intel.com>

== Series Details ==

Series: tests/gem_shrink: Exercise OOM and other routes to shrinking in reasonable time (rev2)
URL   : https://patchwork.freedesktop.org/series/54746/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_5369 -> IGTPW_2191
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with IGTPW_2191 absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in IGTPW_2191, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  External URL: https://patchwork.freedesktop.org/api/1.0/series/54746/revisions/2/mbox/

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

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

### IGT changes ###

#### Possible regressions ####

  * igt@i915_selftest@live_gtt:
    - fi-kbl-r:           PASS -> DMESG-WARN

  
#### Suppressed ####

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

  * {igt@gem_shrink@reclaims-and-oom-both-basic}:
    - fi-ivb-3520m:       NOTRUN -> DMESG-WARN
    - fi-snb-2520m:       NOTRUN -> DMESG-WARN
    - fi-kbl-8809g:       NOTRUN -> DMESG-WARN
    - fi-glk-j4005:       NOTRUN -> DMESG-WARN
    - fi-cfl-8700k:       NOTRUN -> DMESG-WARN
    - fi-icl-u2:          NOTRUN -> DMESG-WARN
    - fi-kbl-7500u:       NOTRUN -> DMESG-WARN
    - fi-bdw-gvtdvm:      NOTRUN -> DMESG-WARN
    - fi-kbl-x1275:       NOTRUN -> DMESG-WARN
    - fi-kbl-guc:         NOTRUN -> DMESG-WARN
    - fi-kbl-7567u:       NOTRUN -> DMESG-WARN
    - fi-icl-u3:          NOTRUN -> DMESG-WARN
    - fi-skl-guc:         NOTRUN -> DMESG-WARN
    - fi-bxt-j4205:       NOTRUN -> DMESG-WARN
    - fi-skl-6700hq:      NOTRUN -> DMESG-WARN
    - fi-bsw-kefka:       NOTRUN -> DMESG-WARN
    - fi-ivb-3770:        NOTRUN -> DMESG-WARN
    - fi-skl-6700k2:      NOTRUN -> DMESG-WARN
    - fi-hsw-4770:        NOTRUN -> DMESG-WARN
    - fi-kbl-7560u:       NOTRUN -> DMESG-WARN
    - fi-skl-6600u:       NOTRUN -> DMESG-WARN
    - fi-apl-guc:         NOTRUN -> DMESG-WARN
    - fi-kbl-r:           NOTRUN -> DMESG-WARN
    - fi-byt-j1900:       NOTRUN -> DMESG-WARN
    - fi-blb-e6850:       NOTRUN -> DMESG-WARN
    - fi-cfl-8109u:       NOTRUN -> DMESG-WARN
    - fi-bdw-5557u:       NOTRUN -> DMESG-WARN
    - fi-elk-e7500:       NOTRUN -> DMESG-WARN
    - fi-hsw-4770r:       NOTRUN -> DMESG-WARN
    - fi-byt-n2820:       NOTRUN -> DMESG-WARN
    - fi-skl-6260u:       NOTRUN -> DMESG-WARN
    - fi-skl-iommu:       NOTRUN -> DMESG-WARN
    - fi-ilk-650:         NOTRUN -> DMESG-WARN
    - fi-skl-6770hq:      NOTRUN -> DMESG-WARN
    - fi-whl-u:           NOTRUN -> DMESG-WARN
    - fi-cfl-guc:         NOTRUN -> DMESG-WARN

  * {igt@gem_shrink@reclaims-and-oom-userptr-basic}:
    - fi-bwr-2160:        NOTRUN -> FAIL +1

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

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

### IGT changes ###

#### Issues hit ####

  * igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence:
    - fi-byt-clapper:     PASS -> FAIL [fdo#103191] / [fdo#107362]

  * igt@prime_vgem@basic-fence-flip:
    - fi-gdg-551:         PASS -> FAIL [fdo#103182]

  
#### Possible fixes ####

  * igt@gem_mmap_gtt@basic-small-copy:
    - fi-glk-dsi:         INCOMPLETE [fdo#103359] / [k.org#198133] -> PASS

  * igt@i915_selftest@live_coherency:
    - fi-gdg-551:         DMESG-FAIL [fdo#107164] -> PASS

  * igt@i915_selftest@live_hangcheck:
    - fi-bwr-2160:        DMESG-FAIL [fdo#108735] -> PASS

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

  [fdo#103182]: https://bugs.freedesktop.org/show_bug.cgi?id=103182
  [fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
  [fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359
  [fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
  [fdo#107164]: https://bugs.freedesktop.org/show_bug.cgi?id=107164
  [fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
  [fdo#108735]: https://bugs.freedesktop.org/show_bug.cgi?id=108735
  [fdo#109241]: https://bugs.freedesktop.org/show_bug.cgi?id=109241
  [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133


Participating hosts (49 -> 44)
------------------------------

  Additional (1): fi-pnv-d510 
  Missing    (6): fi-kbl-soraka fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-icl-y fi-snb-2600 


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

    * IGT: IGT_4756 -> IGTPW_2191

  CI_DRM_5369: 4d637a8d160356f01d22695ec1a76858bfb55758 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_2191: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2191/
  IGT_4756: 75081c6bfb9998bd7cbf35a7ac0578c683fe55a8 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools



== Testlist changes ==

+igt@gem_shrink@reclaims-and-oom
+igt@gem_shrink@reclaims-and-oom-basic
+igt@gem_shrink@reclaims-and-oom-both
+igt@gem_shrink@reclaims-and-oom-both-basic
+igt@gem_shrink@reclaims-and-oom-userptr
+igt@gem_shrink@reclaims-and-oom-userptr-basic

== Logs ==

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

  parent reply	other threads:[~2019-01-07 18:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 15:37 [Intel-gfx] [PATCH i-g-t] tests/gem_shrink: Exercise OOM and other routes to shrinking in reasonable time Tvrtko Ursulin
2019-01-04 16:05 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-01-04 16:57 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-01-07 11:01 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2019-01-07 11:12   ` Tvrtko Ursulin
2019-01-07 11:28     ` Petri Latvala
2019-01-07 17:33       ` Tvrtko Ursulin
2019-01-07 12:27 ` Michał Winiarski
2019-01-07 12:31   ` Chris Wilson
2019-01-07 12:52     ` Tvrtko Ursulin
2019-01-07 12:56       ` Chris Wilson
2019-01-07 17:36 ` [igt-dev] [PATCH i-g-t v2] " Tvrtko Ursulin
2019-01-07 18:22   ` [igt-dev] [PATCH i-g-t v3] " Tvrtko Ursulin
2019-01-08 10:57     ` [igt-dev] [Intel-gfx] " Chris Wilson
2019-01-07 18:00 ` Patchwork [this message]
2019-01-07 18:25   ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/gem_shrink: Exercise OOM and other routes to shrinking in reasonable time (rev2) Tvrtko Ursulin
2019-01-07 20:53     ` Chris Wilson
2019-01-07 21:43       ` Chris Wilson
2019-01-07 19:24 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/gem_shrink: Exercise OOM and other routes to shrinking in reasonable time (rev3) Patchwork
2019-01-07 22:15 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190107180035.25009.4910@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox