On Fri, Jan 17, 2020 at 08:34:01AM -0500, Aaron Conole wrote: > Bruce Richardson <bruce.richard...@intel.com> writes: > > > On Fri, Jan 17, 2020 at 08:16:55AM -0500, Aaron Conole wrote: > >> Bruce Richardson <bruce.richard...@intel.com> writes: > >> > >> > When werror is set for the build, we should pass that flag through to > >> > sphinx so that it can flag warnings as errors too. > >> > > >> > Signed-off-by: Bruce Richardson <bruce.richard...@intel.com> > >> > --- > >> > >> I see that this actually works to generate the errors... BUT > >> > >> if we merge this it will break the build. Can you also insert a patch > >> to address the warning so that the series could be merged? > >> > > > > Ok, I didn't have any warnings in my setup, which is why I didn't see any > > problems. I assume that the warnings are showing up in travis? Anywhere > > else? > > I only saw them on Travis. > The error from sphinx in travis looks like a false positive that is fixed in later versions of sphinx. The error I see is:
/home/travis/build/bruce-richardson/dpdk/doc/guides/linux_gsg/eal_args.include.rst:: WARNING: document isn't included in any toctree However, that file is an include one that is included in both the linux and freebsd eal parameters docs, and so is not missing though not included in the index. What is the best approach to deal with this, do you think? * rework so it has a toctree entry e.g. by creating a new section for common parameters * other workaround in the code, e.g. rename the file to not end in .rst * can we update sphinx in the travis build to avoid the warning altogether? /Bruce
