From: Vignesh Raman <vignesh.raman@collabora.com>
To: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>,
daniels@collabora.com, igt-dev@lists.freedesktop.org
Cc: helen.koike@collabora.com
Subject: Re: [igt-dev] [PATCH i-g-t v3] lib/igt_kms: Fix memory corruption
Date: Thu, 9 Nov 2023 19:22:54 +0530 [thread overview]
Message-ID: <ce2dfbb2-291e-81b3-f4c3-3dbcf4cce4bf@collabora.com> (raw)
In-Reply-To: <5214fd60-8fde-13c8-f3ec-02391d846ae6@collabora.com>
Hi Bhanu,
On 09/11/23 19:11, Vignesh Raman wrote:
> Hi Bhanu,
>
> On 09/11/23 17:19, Modem, Bhanuprakash wrote:
>> Hi Vignesh,
>>
>> As we introduced the IGT documentation[1] to generate the testlist, we
>> need a fix in few kms tests to compile the IGT.
>>
>> Also, needs few changes in intel-ci/ to avoid noise in the CI.
>>
>> [1]:
>> https://cgit.freedesktop.org/drm/igt-gpu-tools/tree/docs/test_documentation.md
>
> Are you referring to the pipeline failures in
> https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/1029126
>
> In my forked branch the pipeline fails in containers stage,
> https://gitlab.freedesktop.org/vigneshraman/igt-gpu-tools/-/pipelines/1030263
>
> Is there a way to run the pipeline in my fork or should I
> locally build docs (build igt-gpu-tools-doc) with the patch
> and check the issue?
I can reproduce the error with,
scripts/igt_doc.py --config tests/intel/kms_test_config.json --rest
docs/testplan/kms_tests.rst --check-testlist --igt-build-path build/
I will check these warnings.
Regards,
Vignesh
prev parent reply other threads:[~2023-11-09 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 6:29 [igt-dev] [PATCH i-g-t v3] lib/igt_kms: Fix memory corruption Vignesh Raman
2023-11-08 6:42 ` [igt-dev] ✗ Fi.CI.BUILD: failure for lib/igt_kms: Fix memory corruption (rev3) Patchwork
2023-11-08 6:48 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2023-11-08 15:18 ` [igt-dev] [PATCH i-g-t v3] lib/igt_kms: Fix memory corruption Helen Koike
2023-11-08 18:58 ` Daniel Stone
2023-11-09 11:49 ` Modem, Bhanuprakash
2023-11-09 13:41 ` Vignesh Raman
2023-11-09 13:52 ` Vignesh Raman [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=ce2dfbb2-291e-81b3-f4c3-3dbcf4cce4bf@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=bhanuprakash.modem@intel.com \
--cc=daniels@collabora.com \
--cc=helen.koike@collabora.com \
--cc=igt-dev@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