Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Anusha <anusha.srivatsa@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for HuC Update for BXT
Date: Fri, 30 Nov 2018 19:54:17 -0000	[thread overview]
Message-ID: <20181130195417.17611.29711@emeril.freedesktop.org> (raw)
In-Reply-To: <20181130190506.1360-1-anusha.srivatsa@intel.com>

== Series Details ==

Series: HuC Update for BXT
URL   : https://patchwork.freedesktop.org/series/53332/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_5236 -> Patchwork_10982
====================================================

Summary
-------

  **FAILURE**

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

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

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

### IGT changes ###

#### Possible regressions ####

  * igt@i915_selftest@live_execlists:
    - fi-skl-6700hq:      PASS -> DMESG-WARN

  * igt@i915_selftest@live_hangcheck:
    - fi-whl-u:           PASS -> DMESG-FAIL

  * {igt@runner@aborted}:
    - fi-skl-6700hq:      NOTRUN -> FAIL

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

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

### IGT changes ###

#### Issues hit ####

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

  
#### Possible fixes ####

  * igt@gem_ctx_create@basic-files:
    - fi-bsw-kefka:       DMESG-FAIL [fdo#108656] -> PASS

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

  * igt@prime_vgem@basic-fence-flip:
    - fi-gdg-551:         DMESG-FAIL [fdo#103182] -> 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#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
  [fdo#108656]: https://bugs.freedesktop.org/show_bug.cgi?id=108656


Participating hosts (48 -> 43)
------------------------------

  Additional (1): fi-pnv-d510 
  Missing    (6): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 


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

    * Linux: CI_DRM_5236 -> Patchwork_10982

  CI_DRM_5236: f9cd6a3ffb4400071d46dd123347802c1422d9da @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4736: 285ebfb3b7adc56586031afa5150c4e5ad40c229 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_10982: a68b5ec5b6671c7f587a077d89fd7e34d07ea4e5 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

a68b5ec5b667 HAX enable HuC for CI
70d9dcefa690 firmware/huc/BXT: Update the HuC version

== Logs ==

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

      parent reply	other threads:[~2018-11-30 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30 19:05 [PATCH 0/2] HuC Update for BXT Anusha
2018-11-30 19:05 ` [PATCH 1/2] firmware/huc/BXT: Update the HuC version Anusha
2018-11-30 19:05 ` [PATCH 2/2] HAX enable HuC for CI Anusha
2018-11-30 19:30 ` ✗ Fi.CI.CHECKPATCH: warning for HuC Update for BXT Patchwork
2018-11-30 19:54 ` Patchwork [this message]

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=20181130195417.17611.29711@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=anusha.srivatsa@intel.com \
    --cc=intel-gfx@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