From: David Marchand <david.marchand@redhat.com>
To: Aaron Conole <aconole@redhat.com>
Cc: Harry van Haaren <harry.van.haaren@intel.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [BUG] service_lcore_en_dis_able from service_autotest failing
Date: Wed, 4 Sep 2019 11:55:23 +0200 [thread overview]
Message-ID: <CAJFAV8zAUa=B9JhF6NZJHhLS-Jnt-0aW9hzXVHZiz=Q0QR_8Zg@mail.gmail.com> (raw)
In-Reply-To: <f7tblw130bp.fsf@dhcp-25.97.bos.redhat.com>
On Tue, Sep 3, 2019 at 4:46 PM Aaron Conole <aconole@redhat.com> wrote:
>
> Hi Harry,
>
> I noticed as part of series_6218
> (http://patches.dpdk.org/project/dpdk/list/?series=6218) that the travis
> build had a single failure, in service_autotest but it doesn't seem
> related to the series at all.
>
> https://travis-ci.com/ovsrobot/dpdk/jobs/230358460
>
> Not sure if there's some kind of debugging we can add or look at to help
> diagnose failures when they occur. Do you have time to have a look?
My two cents.
TEST_ASSERT_EQUAL maps to RTE_TEST_ASSERT which only displays failed
assert at DEBUG level.
I'd say we should change this to ERR level.
I can see you can define a RTE_TEST_TRACE_FAILURE macro too before
including "test.h" (which includes rte_test.h).
Never touched this before though.
--
David Marchand
prev parent reply other threads:[~2019-09-04 9:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 14:45 Aaron Conole
2019-09-04 9:41 ` Van Haaren, Harry
2019-09-04 10:04 ` David Marchand
2019-09-04 10:38 ` David Marchand
2019-09-04 19:56 ` Aaron Conole
2019-10-07 9:50 ` Van Haaren, Harry
2019-10-07 12:38 ` Aaron Conole
2019-10-14 14:53 ` Aaron Conole
2019-10-14 16:48 ` Van Haaren, Harry
2019-10-15 16:42 ` Van Haaren, Harry
2019-09-04 9:55 ` David Marchand [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='CAJFAV8zAUa=B9JhF6NZJHhLS-Jnt-0aW9hzXVHZiz=Q0QR_8Zg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
/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).