On machines that I see test failures -- sometimes, frequently, they disappear when I use make test-debug rather than make test.
Burt On Thu, Mar 22, 2018 at 2:08 PM, Klement Sekera <ksek...@cisco.com> wrote: > > > > Ooo, I see... So, yeah, I have to hop between a local branch and > the > > upstream master, > > so I may be being victimized by this problem. I've been doing a > "make > > wipe" or "wipe-release" > > and forgot about the industrial 'git clean'. Drat. I'll give > that a run... > > > > > > And for the record, I have rebuilt at this commit: > > > > commit 6f4a6be8f222dd8caa94d19a7e4d87cb864ba7f4 > > Author: Neale Ranns <nra...@cisco.com <mailto:nra...@cisco.com> > > > Date: Fri Mar 16 16:26:21 2018 -0700 > > > > Interface Unicast, Multicast and Broadcast stats on the API > > > > Change-Id: I7c75da358aff1bd0216a602a49f2909cef5d920d > > Signed-off-by: Neale Ranns <nra...@cisco.com > > <mailto:nra...@cisco.com> > > > > > In a"git clean -fxd" directory and still see the PAPI "make test" errors. > > > > I can't reproduce this ... the thought that this could be a timing issue > popped into my head, but I just passed 15 iterations of git clean & make > test-debug and did not see the issue. Maybe it (the timing issue) depends > on the number of cores ... how many cores do you have on the box? > > > >
