All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: "Peres, Martin" <martin.peres@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.BAT: failure for Extend BT2020 support in iCSC and fixes (rev5)
Date: Tue, 2 Jul 2019 13:23:28 +0000	[thread overview]
Message-ID: <E7C9878FBA1C6D42A1CA3F62AEB6945F820EE616@BGSMSX104.gar.corp.intel.com> (raw)
In-Reply-To: <56A4AB1F0E1B5D4C83D27F43C50F662E58FE8DDD@IRSMSX107.ger.corp.intel.com>



>-----Original Message-----
>From: Peres, Martin
>Sent: Monday, July 1, 2019 7:05 PM
>To: Shankar, Uma <uma.shankar@intel.com>; intel-gfx@lists.freedesktop.org
>Subject: Re: ✗ Fi.CI.BAT: failure for Extend BT2020 support in iCSC and fixes (rev5)
>
>On 28/06/2019 18:06, Shankar, Uma wrote:
>>
>>
>>> -----Original Message-----
>>> From: Patchwork [mailto:patchwork@emeril.freedesktop.org]
>>> Sent: Friday, June 28, 2019 8:34 PM
>>> To: Shankar, Uma <uma.shankar@intel.com>
>>> Cc: intel-gfx@lists.freedesktop.org
>>> Subject: ✗ Fi.CI.BAT: failure for Extend BT2020 support in iCSC and
>>> fixes (rev5)
>>>
>>> == Series Details ==
>>>
>>> Series: Extend BT2020 support in iCSC and fixes (rev5)
>>> URL   : https://patchwork.freedesktop.org/series/60480/
>>> State : failure
>>>
>>> == Summary ==
>>>
>>> CI Bug Log - changes from CI_DRM_6379 -> Patchwork_13466
>>> ====================================================
>>>
>>> Summary
>>> -------
>>>
>>>  **FAILURE**
>>>
>>>  Serious unknown changes coming with Patchwork_13466 absolutely need
>>> to be  verified manually.
>>>
>>>  If you think the reported changes have nothing to do with the
>>> changes  introduced in Patchwork_13466, please notify your bug team
>>> to allow them  to document this new failure mode, which will reduce false
>positives in CI.
>>>
>>>  External URL:
>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/
>>>
>>> Possible new issues
>>> -------------------
>>>
>>>  Here are the unknown changes that may have been introduced in
>Patchwork_13466:
>>>
>>> ### IGT changes ###
>>>
>>> #### Possible regressions ####
>>>
>>>  * igt@i915_selftest@live_mman:
>>>    - fi-bsw-n3050:       [PASS][1] -> [DMESG-WARN][2]
>>>   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6379/fi-bsw-
>>> n3050/igt@i915_selftest@live_mman.html
>>>   [2]:
>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/fi-bsw-
>>> n3050/igt@i915_selftest@live_mman.html
>>>
>>
>> Hi Martin,
>> This doesn't seem to be related to this change.
>>
>> Please check once and update this.
>
>New bug filed: https://bugs.freedesktop.org/show_bug.cgi?id=111037
>
>I've queued re-reporting which should start the shards result.
>
>Thanks!

Thanks Martin.
CI.BAT now shows a Green, but CI.IGT result is still not generated. 
Should we wait or it needs to be triggered separately. We have CI.IGT a green
on trybot though.

Regards,
Uma Shankar

>Martin
>
>>
>> Thanks & Regards,
>> Uma Shankar
>>
>>> Known issues
>>> ------------
>>>
>>>  Here are the changes found in Patchwork_13466 that come from known issues:
>>>
>>> ### IGT changes ###
>>>
>>> #### Issues hit ####
>>>
>>>  * igt@i915_pm_rpm@module-reload:
>>>    - fi-kbl-r:           [PASS][3] -> [DMESG-WARN][4] ([fdo#111012])
>>>   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6379/fi-kbl-
>>> r/igt@i915_pm_rpm@module-reload.html
>>>   [4]:
>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/fi-kbl-
>>> r/igt@i915_pm_rpm@module-reload.html
>>>
>>>
>>> #### Possible fixes ####
>>>
>>>  * igt@gem_mmap_gtt@basic-write-gtt-no-prefault:
>>>    - fi-icl-u3:          [DMESG-WARN][5] ([fdo#107724]) -> [PASS][6] +1 similar issue
>>>   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6379/fi-icl-
>>> u3/igt@gem_mmap_gtt@basic-write-gtt-no-prefault.html
>>>   [6]:
>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/fi-icl-
>>> u3/igt@gem_mmap_gtt@basic-write-gtt-no-prefault.html
>>>
>>>  * igt@kms_frontbuffer_tracking@basic:
>>>    - fi-hsw-peppy:       [DMESG-WARN][7] ([fdo#102614]) -> [PASS][8]
>>>   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6379/fi-hsw-
>>> peppy/igt@kms_frontbuffer_tracking@basic.html
>>>   [8]:
>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/fi-hsw-
>>> peppy/igt@kms_frontbuffer_tracking@basic.html
>>>
>>>
>>>  [fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614
>>>  [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
>>>  [fdo#111012]: https://bugs.freedesktop.org/show_bug.cgi?id=111012
>>>
>>>
>>> Participating hosts (51 -> 45)
>>> ------------------------------
>>>
>>>  Additional (2): fi-icl-dsi fi-skl-gvtdvm
>>>  Missing    (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-
>icl-
>>> y fi-byt-clapper fi-bdw-samus
>>>
>>>
>>> Build changes
>>> -------------
>>>
>>>  * Linux: CI_DRM_6379 -> Patchwork_13466
>>>
>>>  CI_DRM_6379: 12f8aba06508afb9b668a2496b2fb296ed21e377 @
>>> git://anongit.freedesktop.org/gfx-ci/linux
>>>  IGT_5072: 5f6cf7070b249975bac4d747a9c44d81c94c4381 @
>>> git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>>>  Patchwork_13466: a1cff9784bf59b14027b36876e4aaff7ab8b9599 @
>>> git://anongit.freedesktop.org/gfx-ci/linux
>>>
>>>
>>> == Kernel 32bit build ==
>>>
>>> Warning: Kernel 32bit buildtest failed:
>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/build_32bit.
>>> log
>>>
>>>  CALL    scripts/checksyscalls.sh
>>>  CALL    scripts/atomic/check-atomics.sh
>>>  CHK     include/generated/compile.h
>>> Kernel: arch/x86/boot/bzImage is ready  (#1)  Building modules, stage
>>> 2.
>>>  MODPOST 112 modules
>>> ERROR: "__udivdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>>> ERROR: "__divdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>>> scripts/Makefile.modpost:91: recipe for target '__modpost' failed
>>> make[1]: *** [__modpost] Error 1
>>> Makefile:1287: recipe for target 'modules' failed
>>> make: *** [modules] Error 2
>>>
>>>
>>> == Linux commits ==
>>>
>>> a1cff9784bf5 drm/i915/icl: Fixed Input CSC Co-efficients for
>>> BT601/709
>>> 3caa5b4db153 drm/i915/icl: Fix Y pre-offset for Full Range YCbCr
>>> d4e7995252df
>>> drm/i915/icl: Handle YCbCr to RGB conversion for BT2020 case
>>>
>>> == Logs ==
>>>
>>> For more details see:
>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/
>>

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-07-02 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28  8:02 [v5 0/3] Extend BT2020 support in iCSC and fixes Uma Shankar
2019-06-28  8:02 ` [v5 1/3] drm/i915/icl: Handle YCbCr to RGB conversion for BT2020 case Uma Shankar
2019-06-28  8:02 ` [v5 2/3] drm/i915/icl: Fix Y pre-offset for Full Range YCbCr Uma Shankar
2019-06-28  8:02 ` [v5 3/3] drm/i915/icl: Fixed Input CSC Co-efficients for BT601/709 Uma Shankar
2019-06-28 15:03 ` ✗ Fi.CI.BAT: failure for Extend BT2020 support in iCSC and fixes (rev5) Patchwork
2019-06-28 15:06   ` Shankar, Uma
2019-07-01 13:35     ` Peres, Martin
2019-07-02 13:23       ` Shankar, Uma [this message]
2019-07-01 13:36 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-02 19:00 ` ✓ Fi.CI.IGT: " Patchwork
2019-07-04 13:58   ` Shankar, Uma
2019-07-10 12:46     ` Ville Syrjälä

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=E7C9878FBA1C6D42A1CA3F62AEB6945F820EE616@BGSMSX104.gar.corp.intel.com \
    --to=uma.shankar@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=martin.peres@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 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.