public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: Petri Latvala <petri.latvala@intel.com>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_cursor_crc: start crc only once per test (rev4)
Date: Thu, 28 Nov 2019 16:57:26 +0200	[thread overview]
Message-ID: <1cafdc2a-25e7-8c11-9bd0-9f93d2ca4868@gmail.com> (raw)
In-Reply-To: <20191128133920.GV25209@platvala-desk.ger.corp.intel.com>

On 28.11.2019 15.39, Petri Latvala wrote:
> On Thu, Nov 28, 2019 at 01:29:51PM +0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: tests/kms_cursor_crc: start crc only once per test (rev4)
>> URL   : https://patchwork.freedesktop.org/series/70061/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from CI_DRM_7431_full -> IGTPW_3768_full
>> ====================================================
>>
>> Summary
>> -------
>>
>>    **FAILURE**
>>
>>    Serious unknown changes coming with IGTPW_3768_full absolutely need to be
>>    verified manually.
>>    
>>    If you think the reported changes have nothing to do with the changes
>>    introduced in IGTPW_3768_full, 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/IGTPW_3768/index.html
>>
>> Possible new issues
>> -------------------
>>
>>    Here are the unknown changes that may have been introduced in IGTPW_3768_full:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>>    * igt@i915_selftest@live_blt:
>>      - shard-hsw:          [PASS][1] -> [DMESG-FAIL][2]
>>     [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7431/shard-hsw8/igt@i915_selftest@live_blt.html
>>     [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3768/shard-hsw1/igt@i915_selftest@live_blt.html
>>
>>    * igt@kms_cursor_crc@pipe-c-cursor-128x42-sliding:
>>      - shard-iclb:         NOTRUN -> [DMESG-WARN][3]
>>     [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3768/shard-iclb3/igt@kms_cursor_crc@pipe-c-cursor-128x42-sliding.html
> 
> 
> 
> <3> [544.041813] [drm:drm_crtc_add_crc_entry] *ERROR* Overflow of CRC buffer, userspace reads too slow.
> 

Ya, I noticed that too. There's those fb being painted during test and 
it seems those need to be rendered in setup and used from buffered 
versions. I'll look into it, it probably shave off some extra time from 
these tests -- though no hundreds of second to shave off anymore :D


/Juha-Pekka
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2019-11-28 14:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 12:19 [igt-dev] [PATCH i-g-t] tests/kms_cursor_crc: start crc only once per test Juha-Pekka Heikkila
2019-11-27 12:56 ` [igt-dev] ✗ GitLab.Pipeline: warning for tests/kms_cursor_crc: start crc only once per test (rev3) Patchwork
2019-11-27 13:21   ` Petri Latvala
2019-11-27 13:40     ` Arkadiusz Hiler
2019-11-27 13:43       ` Petri Latvala
2019-11-27 13:30 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-11-27 14:03 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_cursor_crc: start crc only once per test (rev4) Patchwork
2019-11-27 14:22 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-11-28 11:34 ` [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_cursor_crc: start crc only once per test (rev3) Patchwork
2019-11-28 12:32 ` [igt-dev] [PATCH i-g-t] tests/kms_cursor_crc: start crc only once per test Petri Latvala
2019-11-28 13:29 ` [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_cursor_crc: start crc only once per test (rev4) Patchwork
2019-11-28 13:39   ` Petri Latvala
2019-11-28 14:57     ` Juha-Pekka Heikkila [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=1cafdc2a-25e7-8c11-9bd0-9f93d2ca4868@gmail.com \
    --to=juhapekka.heikkila@gmail.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@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