From: "Michał Grzelak" <michal.grzelak@intel.com>
To: "Sharma, Swati2" <swati2.sharma@intel.com>
Cc: "Michał Grzelak" <michal.grzelak@intel.com>,
igt-dev@lists.freedesktop.org,
"Mohammed Thasleem" <mohammed.thasleem@intel.com>
Subject: Re: [PATCH i-g-t v4 0/4] kms_flip: limit number of subtests run
Date: Fri, 13 Feb 2026 10:12:26 +0100 (CET) [thread overview]
Message-ID: <1346f34b-bc6f-a900-e37c-a2bbd90f3aa1@intel.com> (raw)
In-Reply-To: <dfc99a00-1369-4575-ba50-95ed3dcf83ea@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
On Thu, 12 Feb 2026, Sharma, Swati2 wrote:
> Hi Michal,
>
> There seems to be build failure with your patches, can you please float new
> rev?
Huh, interesting because I git fetch'ed && git rebase'ed straight
before sending patches. Apparently some conflicting changes must have
been merged after I sent patches, but before they have been applied by
Patchwork, which resulted in build failure:
Patchwork, timestamp of sending to ML:
Subject: [PATCH i-g-t v4 0/4] kms_flip: limit number of subtests run
Date: Thu, 12 Feb 2026 12:10:18 +0100
Conflicting change, git log --oneline --pretty=fuller -- tests/kms_flip.c:
commit 2978b9a78
[...]
CommitDate: Thu Feb 12 13:20:19 2026 +0200
Patchwork, timestamp of patch application:
Subject: ✗ Fi.CI.BUILD: failure for kms_flip: limit number of subtests run (rev3)
Date: Thu, 12 Feb 2026 15:47:28 -0000
Almost impossible to happen, yet still non-zero chances. Let's hope it
won't happen for second time in a row. :)
BR,
Michał
>
> On 12-02-2026 04:40 pm, Michał Grzelak wrote:
>> Next version of [1]. This series addresses both 2x-* and single output
>> tests. This series has been tested on config with 4 outputs connected.
>>
>> [1]
>> https://lore.kernel.org/igt-dev/20260210225546.153728-1-michal.grzelak@intel.com
>>
>> BR,
>> Michał
>>
>> ---
>> Changelog:
>> v3->v4
>> - change \gt into \ge sign
>>
>> v2->v3
>> - ease counting of pairs of outputs
>> - limit number of tested outputs
>> - narrow pair & output limiting to suspend subtests
>> - add separate param for pair and connector limiting
>>
>> v1->v2
>> - split pipe limiting into 2x- and single subtests
>> - add output pair limiting
>>
>>
>>
>> Michał Grzelak (4):
>> tests/kms_flip: test suspend on one pair of pipes
>> tests/kms_flip: run suspend tests on one pipe per output
>> tests/kms_flip: limit output pairs when testing suspend
>> tests/kms_flip: limit number of outputs wrt suspend
>>
>> tests/kms_flip.c | 74 +++++++++++++++++++++++++++++++++++++++---------
>> 1 file changed, 61 insertions(+), 13 deletions(-)
>>
>
prev parent reply other threads:[~2026-02-13 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 11:10 [PATCH i-g-t v4 0/4] kms_flip: limit number of subtests run Michał Grzelak
2026-02-12 11:10 ` [PATCH i-g-t v4 1/4] tests/kms_flip: test suspend on one pair of pipes Michał Grzelak
2026-02-12 11:10 ` [PATCH i-g-t v4 2/4] tests/kms_flip: run suspend tests on one pipe per output Michał Grzelak
2026-02-12 11:10 ` [PATCH i-g-t v4 3/4] tests/kms_flip: limit output pairs when testing suspend Michał Grzelak
2026-02-12 11:10 ` [PATCH i-g-t v4 4/4] tests/kms_flip: limit number of outputs wrt suspend Michał Grzelak
2026-02-12 15:47 ` ✗ Fi.CI.BUILD: failure for kms_flip: limit number of subtests run (rev3) Patchwork
2026-02-12 19:53 ` [PATCH i-g-t v4 0/4] kms_flip: limit number of subtests run Sharma, Swati2
2026-02-13 9:12 ` Michał Grzelak [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=1346f34b-bc6f-a900-e37c-a2bbd90f3aa1@intel.com \
--to=michal.grzelak@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mohammed.thasleem@intel.com \
--cc=swati2.sharma@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