From: "Kazlauskas, Nicholas" <Nicholas.Kazlauskas@amd.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests: Add variable refresh rate tests (rev2)
Date: Fri, 25 Jan 2019 15:21:24 +0000 [thread overview]
Message-ID: <22082500-9ea8-d972-ff4b-e36f29222b7c@amd.com> (raw)
In-Reply-To: <20190125095753.GG4038@platvala-desk.ger.corp.intel.com>
On 1/25/19 4:57 AM, Petri Latvala wrote:
> On Thu, Jan 10, 2019 at 11:09:09AM +0000, Patchwork wrote:
>> == 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
>>
>
>
> Just about all of these failures are this:
>
>
> (kms_cursor_legacy:2598) igt_kms-DEBUG: display: commit {
> (kms_cursor_legacy:2598) igt_kms-CRITICAL: Test assertion failure function igt_pipe_commit, file ../lib/igt_kms.c:2780:
> (kms_cursor_legacy:2598) igt_kms-CRITICAL: Failed assertion: pipe->props[i]
> (kms_cursor_legacy:2598) igt_core-INFO: Stack trace:
> (kms_cursor_legacy:2598) igt_core-INFO: #0 ../lib/igt_core.c:1472 __igt_fail_assert()
> (kms_cursor_legacy:2598) igt_core-INFO: #1 ../lib/igt_kms.c:2782 igt_pipe_commit()
> (kms_cursor_legacy:2598) igt_core-INFO: #2 ../lib/igt_kms.c:3313 do_display_commit()
> (kms_cursor_legacy:2598) igt_core-INFO: #3 ../lib/igt_kms.c:3428 igt_display_commit2()
> (kms_cursor_legacy:2598) igt_core-INFO: #4 ../tests/kms_cursor_legacy.c:522 basic_flip_cursor()
> (kms_cursor_legacy:2598) igt_core-INFO: #5 ../tests/kms_cursor_legacy.c:1491 __real_main1358()
> (kms_cursor_legacy:2598) igt_core-INFO: #6 ../tests/kms_cursor_legacy.c:1358 main()
> (kms_cursor_legacy:2598) igt_core-INFO: #7 ../csu/libc-start.c:344 __libc_start_main()
> (kms_cursor_legacy:2598) igt_core-INFO: #8 [_start+0x2a]
>
I think that's expected.
The vrr_enabled property is a default one in the kernel for 5.0+ but
doesn't exist before that. Since it's default and could affect other
test results if left enabled from another test I chose to add it to the
list of default properties being reset. So it was probably missing the
property in those tests and failing.
I don't know which version of the kernel was running the test but I
don't think it was 5.0 at least (considering the date it ran).
Nicholas Kazlauskas
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-01-25 15:21 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 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests: Add variable refresh rate tests (rev2) Patchwork
2019-01-25 9:57 ` Petri Latvala
2019-01-25 15:21 ` Kazlauskas, Nicholas [this message]
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=22082500-9ea8-d972-ff4b-e36f29222b7c@amd.com \
--to=nicholas.kazlauskas@amd.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 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.