From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Vizzarro <luca.vizzarro@arm.com>
Cc: dev@dpdk.org, Paul Szczepanek <paul.szczepanek@arm.com>,
Patrick Robb <probb@iol.unh.edu>
Subject: Re: [PATCH] dts: fix API doc build warnings
Date: Wed, 20 Nov 2024 16:54:42 +0100 [thread overview]
Message-ID: <2371296.bcXerOTE6V@thomas> (raw)
In-Reply-To: <5896563.1B3tZ46Xf9@thomas>
20/11/2024 16:05, Thomas Monjalon:
> 20/11/2024 15:41, Luca Vizzarro:
> > Sphinx-autodoc issues warnings about some symbols due to bad autodoc
> > "automock"ing when optional dependencies are missing.
> >
> > The current meson setup allows to treat warnings as errors, halting the
> > process and exiting early. Given these warnings should be ignored, this
> > patch removes this behavior.
>
> So the patch is not fixing warnings, it allows them.
> I will change the title.
>
> > Until optional dependencies are enforced,
> > warnings for DTS API docs will be checked manually as part of the DTS
> > approval process.
>
> No, optional dependencies should never be enforced.
>
> [...]
> > -if get_option('werror')
> > - extra_sphinx_args += '-W'
> > -endif
It makes the CI issue disappear.
Applied with this modified message, thanks for fixing quickly:
doc: allow warnings in Sphinx for DTS
Sphinx-autodoc issues warnings about some symbols due to bad autodoc
"automock"ing when optional dependencies are missing:
Warning, treated as error:
Failed to get a method signature for
framework.config.TestSuiteConfig.convert_from_string:
<classmethod(<function TestSuiteConfig.convert_from_string
at 0x7f1a4ec10790>)> is not a callable object
The current meson setup allows to treat warnings as errors, halting the
process and exiting early. Given these warnings should be ignored, this
patch removes this behavior. Until optional dependencies are detected,
warnings for DTS API docs will be checked manually as part of the DTS
approval process.
Fixes: 6597fa4a30ad ("dts: add autodoc Pydantic")
Signed-off-by: Luca Vizzarro <luca.vizzarro@arm.com>
next prev parent reply other threads:[~2024-11-20 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 14:41 Luca Vizzarro
2024-11-20 15:05 ` Thomas Monjalon
2024-11-20 15:54 ` Thomas Monjalon [this message]
2024-11-20 15:56 ` Patrick Robb
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=2371296.bcXerOTE6V@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
/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;
as well as URLs for NNTP newsgroup(s).