Hi Bernhard,
The test does work, but it looks like on github there is a reference file
missing.
Actually I built the test for development purpose only in order to check the
correct
working of the code .. a small sanity check.
I update the github with the missing file.
- Peter
On 02/10/16 19:54, Bernhard Schmidt wrote:
> Hi,
>
> I'm currently working on the Debian packaging of nfdump. One sideeffect
> of switching to modern packaging helper is the testsuite (make check)
> being run by default. The testsuite always fails with this error
>
> make check-TESTS
> make[4]: Entering directory '/build/nfdump-1.6.15/bin'
> make[5]: Entering directory '/build/nfdump-1.6.15/bin'
> PASS: nftest
> FAIL: test.sh
> =======================================
> nfdump 1.6.15: bin/test-suite.log
> =======================================
>
> # TOTAL: 2
> # PASS: 1
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: test.sh
> =============
>
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv4 32bit packets 32bit bytes
> IPv6 32bit packets 32bit bytes
> IPv6 32bit packets 32bit bytes
> IPv6 32bit packets 64bit bytes
> IPv6 64bit packets 32bit bytes
> IPv6 64bit packets 64bit bytes
> IPv4 32bit packets 64bit bytes
> IPv4 64bit packets 32bit bytes
> IPv4 64bit packets 64bit bytes
> 4 bytes interfaces, 2 bytes AS numbers 24 25
> 2 bytes interfaces, 4 bytes AS numbers 25 27
> 4 bytes interfaces, 4 bytes AS numbers 26 29
> diff: nfdump.test.out: No such file or directory
> FAIL test.sh (exit status: 2)
>
> ============================================================================
> Testsuite summary for nfdump 1.6.15
> ============================================================================
> # TOTAL: 2
> # PASS: 1
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See bin/test-suite.log
> Please report to pe...@people.ops-trust.net
> ============================================================================
>
> I had a look at bin/test.sh and I'm confused how this is supposed to
> work. As far as I can see nfgen generates some netflow, then it gets
> processed by nfdump and the output of multiple, different nfdump
> invocations is compared to a file nfdump.test.out that is neither
> shipped nor generated anywhere.
>
> Is this testsuite supposed to work?
>
> Best Regards,
> Bernhard
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Nfdump-discuss mailing list
> Nfdump-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfdump-discuss
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nfdump-discuss mailing list
Nfdump-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfdump-discuss
