Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t] meson_options: Disable testplan by default
Date: Thu, 17 Aug 2023 10:49:06 +0200	[thread overview]
Message-ID: <20230817104906.6fe0feea@maurocar-mobl2> (raw)
In-Reply-To: <20230817054916.525796-1-bhanuprakash.modem@intel.com>

On Thu, 17 Aug 2023 11:19:16 +0530
Bhanuprakash Modem <bhanuprakash.modem@intel.com> wrote:

> Disable testplan until we fully enabled it.

Not sure why you want to do that.

Disabling it is bad, as it will prevent the system to generate warnings
and errors with broken documentation patches, which ends breaking
several Intel CI reports that depend on them.

If your concern is with regards to documentation, besides the documentation
already inside igt_doc.py, I just sent a patch documenting how testplan docs
work and explaining that the check for i915, KMS and Xe documentation
happens at build time:

	https://patchwork.freedesktop.org/series/122564/

So, please don't merge this change.

Regards,
Mauro

  parent reply	other threads:[~2023-08-17  8:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17  5:49 [igt-dev] [i-g-t] meson_options: Disable testplan by default Bhanuprakash Modem
2023-08-17  7:10 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-08-17  7:41 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-17  8:07 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-08-17  8:08 ` [igt-dev] [i-g-t] " Kamil Konieczny
2023-08-17  8:49 ` Mauro Carvalho Chehab [this message]
2023-08-17 19:21 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork

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=20230817104906.6fe0feea@maurocar-mobl2 \
    --to=mauro.chehab@linux.intel.com \
    --cc=bhanuprakash.modem@intel.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