| Summary: | ASTERISK-27932: [patch] tests/yappcap: Requires rawsocket. | ||
| Reporter: | Alexander Traud (traud) | Labels: | patch pjsip |
| Date Opened: | 2018-06-21 07:34:34 | Date Closed: | 2018-09-11 16:16:07 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Tests/testsuite |
| Versions: | GIT | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) test_rawsocket_yappcap.patch | |
| Description: | This issue was introduced with Commit [e271ae6|http://github.com/asterisk/testsuite/commit/e271ae60af0c0d1065b46961c252e6644fb59cea], Commit [3b6df38|http://github.com/asterisk/testsuite/commit/3b6df38df7bfb727a1a8b63b8ee2fdb31b987086], and Commit [0e03f92|http://github.com/asterisk/testsuite/commit/0e03f92142d096da455797abc87952d518d490bd].
The following seven tests based on the Python module {{yappcap}} require access to rawsocket. If the Asterisk Test Suite is not started with the access permission for rawsockets (like via {{sudo}}), those tests should skip. Currently, they fail. * tests/codecs/opus/fec/jitterbuffer/adaptive * tests/channels/pjsip/transfers/attended_transfer/nominal/callee_local_direct_media * tests/channels/pjsip/transfers/attended_transfer/nominal/caller_local_direct_media * tests/codecs/opus/fec/jitterbuffer/fixed * tests/codecs/opus/fec/no_jitterbuffer * tests/channels/pjsip/subscriptions/presence/verify_bodies/verify_pidf * tests/channels/pjsip/subscriptions/presence/verify_bodies/verify_xpidf | ||
| Comments: | By: Asterisk Team (asteriskteam) 2018-06-21 07:34:36.067-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Corey Farrell (coreyfarrell) 2018-09-11 16:01:16.094-0500 Should this issue be closed as resolved or are additional patches required? By: Richard Mudgett (rmudgett) 2018-09-11 16:16:07.291-0500 Looks like this got merged while autoclose was broken, so yes. | ||