public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for tests: Add variable refresh rate tests (rev2)
Date: Thu, 10 Jan 2019 11:09:09 -0000	[thread overview]
Message-ID: <20190110110909.29235.83227@emeril.freedesktop.org> (raw)
In-Reply-To: <20190109194932.16679-1-nicholas.kazlauskas@amd.com>

== Series Details ==

Series: tests: Add variable refresh rate tests (rev2)
URL   : https://patchwork.freedesktop.org/series/54960/
State : failure

== Summary ==

CI Bug Log - changes from IGT_4758 -> IGTPW_2212
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with IGTPW_2212 absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in IGTPW_2212, 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/54960/revisions/2/

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

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

### IGT changes ###

#### Possible regressions ####

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
    - fi-pnv-d510:        PASS -> FAIL +19

  * igt@kms_pipe_crc_basic@hang-read-crc-pipe-b:
    - fi-blb-e6850:       PASS -> FAIL +18

  * igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence:
    - fi-elk-e7500:       PASS -> FAIL +19

  * igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-frame-sequence:
    - fi-gdg-551:         PASS -> FAIL +19

  * igt@kms_pipe_crc_basic@read-crc-pipe-a:
    - fi-bwr-2160:        PASS -> FAIL +19

  
#### Warnings ####

  * igt@kms_frontbuffer_tracking@basic:
    - fi-elk-e7500:       {SKIP} -> FAIL

  * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
    - fi-blb-e6850:       INCOMPLETE [fdo#107718] -> FAIL

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

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

### IGT changes ###

#### Issues hit ####

  * igt@amdgpu/amd_basic@cs-compute:
    - fi-kbl-8809g:       NOTRUN -> FAIL [fdo#108094]

  * igt@amdgpu/amd_prime@amd-to-i915:
    - fi-kbl-8809g:       NOTRUN -> FAIL [fdo#107341]

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

  
#### Possible fixes ####

  * igt@amdgpu/amd_basic@userptr:
    - fi-kbl-8809g:       DMESG-WARN [fdo#108965] -> PASS

  * igt@pm_rpm@basic-rte:
    - fi-icl-u2:          DMESG-WARN [fdo#108654] -> PASS

  * igt@pm_rpm@module-reload:
    - fi-skl-guc:         INCOMPLETE [fdo#107807] -> PASS

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

  [fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
  [fdo#107341]: https://bugs.freedesktop.org/show_bug.cgi?id=107341
  [fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
  [fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
  [fdo#107807]: https://bugs.freedesktop.org/show_bug.cgi?id=107807
  [fdo#108094]: https://bugs.freedesktop.org/show_bug.cgi?id=108094
  [fdo#108654]: https://bugs.freedesktop.org/show_bug.cgi?id=108654
  [fdo#108965]: https://bugs.freedesktop.org/show_bug.cgi?id=108965
  [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271


Participating hosts (49 -> 43)
------------------------------

  Missing    (6): fi-kbl-soraka fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-icl-y fi-bdw-samus 


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

    * IGT: IGT_4758 -> IGTPW_2212

  CI_DRM_5390: fbad04f7b03cd619517a8455ca973ede0ecb6971 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_2212: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2212/
  IGT_4758: f01796214bbde31e37b0593e547ad9436fdd02ba @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools



== Testlist changes ==

+igt@kms_vrr@flip-basic
+igt@kms_vrr@flip-dpms
+igt@kms_vrr@flip-suspend

== Logs ==

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

  parent reply	other threads:[~2019-01-10 11:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 19:49 [igt-dev] [PATCH i-g-t] tests: Add variable refresh rate tests Nicholas Kazlauskas
2019-01-09 20:20 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2019-01-10 11:09 ` Patchwork [this message]
2019-01-25  9:57   ` [igt-dev] ✗ Fi.CI.BAT: failure for tests: Add variable refresh rate tests (rev2) Petri Latvala
2019-01-25 15:21     ` Kazlauskas, Nicholas
2019-01-25 16:43       ` Saarinen, Jani
2019-01-25 17:21         ` Kazlauskas, Nicholas
2019-01-28 10:41           ` Petri Latvala
2019-01-28 13:46             ` Kazlauskas, Nicholas
2019-01-24 16:04 ` [igt-dev] [PATCH i-g-t] tests: Add variable refresh rate tests Wentland, Harry
2019-01-24 16:59   ` Kazlauskas, Nicholas

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=20190110110909.29235.83227@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=nicholas.kazlauskas@amd.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