[svn-commits] mjordan: testsuite/asterisk/trunk r4858 - /asterisk/trunk/tests/channels/SIP/...

[SVN commits to the Digium repositories]

Author: mjordan
Date: Tue Mar 18 10:35:22 2014
New Revision: 4858

URL: http://svnview.digium.com/svn/testsuite?view=rev&rev=4858
Log:
pcap_demo: skip test due to errors in yappcap/libpcap

The pcap libraries used by yappcap have a bug where they claim they cannot
allocate sufficient memory to being listening for packets. This causes the
pcap_demo test to fail some times with the following exception:

 File "yappcap.pyx", line 490, in yappcap.PcapLive.activate (yappcap.c:4333)
yappcap.PcapError: can't create rx ring on packet socket: Cannot allocate memory

The pcap generation capabilities are still useful in the test suite, but they
don't have to be used all of the time (and in general, are only used when we
need a packet capture from a test). Since this capability is only used when
needed, it doesn't really make sense to continue to have the continuous
integration tests fail due to a problem in yappcap.

Modified:
    asterisk/trunk/tests/channels/SIP/pcap_demo/test-config.yaml

Modified: asterisk/trunk/tests/channels/SIP/pcap_demo/test-config.yaml
URL: http://svnview.digium.com/svn/testsuite/asterisk/trunk/tests/channels/SIP/pcap_demo/test-config.yaml?view=diff&rev=4858&r1=4857&r2=4858
==============================================================================
--- asterisk/trunk/tests/channels/SIP/pcap_demo/test-config.yaml (original)
+++ asterisk/trunk/tests/channels/SIP/pcap_demo/test-config.yaml Tue Mar 18 10:35:22 2014
@@ -1,4 +1,15 @@
 testinfo:
+    # This test is skipped as - on some CentOS 6 build agents - the yappcap
+    # library will throw an exception indicating that it can't allocate memory.
+    # Example:
+    #  File "yappcap.pyx", line 490, in yappcap.PcapLive.activate (yappcap.c:4333)
+    #   yappcap.PcapError: can't create rx ring on packet socket: Cannot allocate memory
+    #
+    # This is a random error and doesn't really preclude the usage of using yappcap
+    # or the pcap generation utilities in the Test Suite when you need it, but it
+    # does make this test unlikely to consistently pass, which is bad for continuous
+    # integration.
+    skip: True
     summary:    'Demo of PCAP and SIPMessage tests'
     description: |
         'Make a simple call and verify via pcap that an INVITE and a 200 happen'