DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Aaron Conole <aconole@redhat.com>
Cc: Phil Yang <phil.yang@arm.com>, dev <dev@dpdk.org>,
	 David Christensen <drc@linux.vnet.ibm.com>,
	 Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	 "Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
	nd <nd@arm.com>, Dodji Seketeli <dodji@redhat.com>,
	 Neil Horman <nhorman@tuxdriver.com>,
	Ray Kinsella <mdr@ashroe.eu>, Harman Kalra <hkalra@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] eal: use c11 atomics for interrupt status
Date: Wed, 8 Jul 2020 15:59:12 +0200	[thread overview]
Message-ID: <CAJFAV8zCutM4iz-iDr_iB4=jt3MNQKSbQ2op_977FDhXJfoNig@mail.gmail.com> (raw)
In-Reply-To: <f7tsge2xguv.fsf@dhcp-25.97.bos.redhat.com>

On Wed, Jul 8, 2020 at 3:43 PM Aaron Conole <aconole@redhat.com> wrote:
> > Note: checking on the test-report ml, I saw nothing, but ovsrobot did
> > catch the issue with this change too, Aaron?
>
> I don't have archives back to Jun 11 on the robot server.  I think it
> doesn't preserve forever (and the archives seem to go back only until
> Jul 03).  I will update it.
>
> I do see that we have a failed travis job:
>
> https://travis-ci.org/github/ovsrobot/dpdk/builds/697180855
>
> I'm surprised this didn't go out.  Have we seen other failures to report
> of the ovs robot recently?  I can double check the job config.
>

We do receive reports from the robot atm.
And I found one failure reported this morning.
http://mails.dpdk.org/archives/test-report/2020-July/142421.html

Maybe transient failures wrt mail delivery?
Just throwing an idea..


-- 
David Marchand


  reply	other threads:[~2020-07-08 13:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 10:24 [dpdk-dev] [PATCH 1/2] eal: remove redundant code Phil Yang
2020-06-11 10:24 ` [dpdk-dev] [PATCH 2/2] eal: use c11 atomics for interrupt status Phil Yang
2020-07-08  5:24   ` Honnappa Nagarahalli
2020-07-08 11:41   ` Harman Kalra
2020-07-09  5:17     ` Phil Yang
2020-07-08 12:29   ` David Marchand
2020-07-08 13:43     ` Aaron Conole
2020-07-08 13:59       ` David Marchand [this message]
2020-07-08 20:48         ` Aaron Conole
2020-07-08 15:04     ` Kinsella, Ray
2020-07-09  5:21       ` Phil Yang
2020-07-08  5:14 ` [dpdk-dev] [PATCH 1/2] eal: remove redundant code Honnappa Nagarahalli
2020-07-08  5:20   ` Phil Yang
2020-07-09  6:46 ` [dpdk-dev] [PATCH v2] eal: use c11 atomic built-ins for interrupt status Phil Yang
2020-07-09  8:02   ` Stefan Puiu
2020-07-09  8:07     ` Phil Yang
2020-07-09  8:34   ` [dpdk-dev] [PATCH v3] " Phil Yang
2020-07-09 10:30     ` David Marchand
2020-07-10  7:18       ` Dodji Seketeli
2020-07-10  6:32     ` David Marchand

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='CAJFAV8zCutM4iz-iDr_iB4=jt3MNQKSbQ2op_977FDhXJfoNig@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dodji@redhat.com \
    --cc=drc@linux.vnet.ibm.com \
    --cc=hkalra@marvell.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=mdr@ashroe.eu \
    --cc=nd@arm.com \
    --cc=nhorman@tuxdriver.com \
    --cc=phil.yang@arm.com \
    --cc=ruifeng.wang@arm.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).