From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] ci: exit setup on any error
Date: Fri, 13 Sep 2019 13:19:47 +0200 [thread overview]
Message-ID: <10817280.cn9q4F5tNv@xps> (raw)
In-Reply-To: <f7t8ss3ivbr.fsf@dhcp-25.97.bos.redhat.com>
08/08/2019 16:30, Aaron Conole:
> David Marchand <david.marchand@redhat.com> writes:
>
> > -e is preferrable so that we can catch errors in the middle of this
> > script.
> > An example is this Travis job [1] that should have errored at the meson
> > install step rather than go to the build step.
> >
> > Adding debug mode as it can help post-mortem.
> >
> > 1: https://travis-ci.com/DPDK/dpdk/jobs/223511683
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > ---
>
> Good call.
>
> Acked-by: Aaron Conole <aconole@redhat.com>
Applied, thanks
prev parent reply other threads:[~2019-09-13 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 12:22 David Marchand
2019-08-08 13:07 ` Michael Santana Francisco
2019-08-08 14:30 ` Aaron Conole
2019-09-13 11:19 ` Thomas Monjalon [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=10817280.cn9q4F5tNv@xps \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).