public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] tests/debugfs: use igt_display_require
Date: Fri, 23 Nov 2018 11:53:31 -0000	[thread overview]
Message-ID: <20181123115331.3991.75454@emeril.freedesktop.org> (raw)
In-Reply-To: <20181122093700.31211-1-daniel.vetter@ffwll.ch>

== Series Details ==

Series: series starting with [i-g-t,1/5] tests/debugfs: use igt_display_require
URL   : https://patchwork.freedesktop.org/series/52867/
State : success

== Summary ==

= CI Bug Log - changes from IGT_4725 -> IGTPW_2086 =

== Summary - SUCCESS ==

  No regressions found.

  External URL: https://patchwork.freedesktop.org/api/1.0/series/52867/revisions/1/mbox/

== Known issues ==

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

  === IGT changes ===

    ==== Issues hit ====

    igt@kms_frontbuffer_tracking@basic:
      fi-hsw-peppy:       PASS -> DMESG-WARN (fdo#102614)

    
    ==== Possible fixes ====

    igt@gem_ctx_create@basic-files:
      fi-icl-u2:          DMESG-WARN (fdo#107724) -> PASS

    igt@i915_selftest@live_contexts:
      fi-kbl-7560u:       INCOMPLETE -> PASS

    
  fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614
  fdo#107724 https://bugs.freedesktop.org/show_bug.cgi?id=107724


== Participating hosts (51 -> 43) ==

  Missing    (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-icl-u3 fi-icl-y 


== Build changes ==

    * IGT: IGT_4725 -> IGTPW_2086

  CI_DRM_5185: 08f3cf2314cc0484a5b332e8dc206e778709bf21 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_2086: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2086/
  IGT_4725: 9dc7c41d1c600133d6e3e63f1941c2e75d23bd3b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools



== Testlist changes ==

+igt@debugfs_test@read_all_entries_display_on

== Logs ==

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

  parent reply	other threads:[~2018-11-23 11:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22  9:36 [igt-dev] [PATCH i-g-t 1/5] tests/debugfs: use igt_display_require Daniel Vetter
2018-11-22  9:36 ` [igt-dev] [PATCH i-g-t 2/5] tests: Use igt_display_require Daniel Vetter
2018-11-22  9:36 ` [igt-dev] [PATCH i-g-t 3/5] lib/kms: Drop igt_display_init Daniel Vetter
2018-11-26 21:37   ` Antonio Argenziano
2018-11-27  8:46     ` Daniel Vetter
2018-11-22  9:36 ` [igt-dev] [PATCH i-g-t 4/5] lib/kms: warn if we commit without outputs Daniel Vetter
2018-11-26 12:33   ` Arkadiusz Hiler
2018-11-22  9:37 ` [igt-dev] [PATCH i-g-t 5/5] lib/kms: Enable outputs by default in igt_require_display Daniel Vetter
2018-11-29 17:18   ` Daniel Vetter
2018-11-23 11:53 ` Patchwork [this message]
2018-11-23 13:18 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/5] tests/debugfs: use igt_display_require 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=20181123115331.3991.75454@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=igt-dev@lists.freedesktop.org \
    /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