From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>,
Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"ci@dpdk.org" <ci@dpdk.org>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Travis not picking documentation warnings/errors
Date: Thu, 16 Jan 2020 16:01:04 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B097553C3D@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8y9O=ByNCQO+AoBD=h31skGD34MoqSy+wz6PFDfX+B6aw@mail.gmail.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of David Marchand
> Sent: Thursday, January 16, 2020 3:31 PM
> To: Aaron Conole <aconole@redhat.com>; Michael Santana
> <maicolgabriel@hotmail.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>; ci@dpdk.org; dev <dev@dpdk.org>
> Subject: [dpdk-dev] Travis not picking documentation warnings/errors
>
> Hello,
>
> We noticed that documentation generation warnings/errors are not being
> reported in Travis.
> I did not look into the details, but it would sure help to catch this
> earlier than when merging in master.
>
> Example: https://travis-ci.com/ovsrobot/dpdk/jobs/275846558
> Look for WARNING:
>
>
Looking at the sphinx docs, it seems -W flag should do what we want.
I'm looking at fixing the stdout/stderr issue with the wrapper script
so I can look to add that flag in while I'm at it.
prev parent reply other threads:[~2020-01-16 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 15:31 David Marchand
2020-01-16 16:01 ` Richardson, Bruce [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=59AF69C657FD0841A61C55336867B5B097553C3D@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
--cc=thomas@monjalon.net \
/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).