[asterisk-bugs] [JIRA] (ASTERISK-25225) testsuite: lua tests using SIPp cannot run on Jenkins

Asterisk Team (JIRA) noreply at issues.asterisk.org
Wed Jul 1 13:57:33 CDT 2015


    [ https://issues.asterisk.org/jira/browse/ASTERISK-25225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226764#comment-226764 ] 

Asterisk Team commented on ASTERISK-25225:
------------------------------------------

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].

> testsuite: lua tests using SIPp cannot run on Jenkins
> -----------------------------------------------------
>
>                 Key: ASTERISK-25225
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25225
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Tests/testsuite
>            Reporter: Matt Jordan
>
> Running any one of the following four tests fails on the Jenkins build agents:
> # SIP/rfc2833_dtmf_detect
> # SIP/sip_channel_params
> # SIP/tcpauthlimit
> # SIP/tcpauthtimeout
> This is because Jenkins build agents are not a big fan of processes trying to open a terminal:
> {noformat}
>       Running ['tests/channels/SIP/rfc2833_dtmf_detect/run-test'] ...
> error while executing sipp/register.xml sipp scenario (sipp exited with status 1)
> Error opening terminal: unknown.
> error running test
> {noformat}
> The Python tests work around this by spawning a process inside a virtual terminal:
> {code}
>         reactor.spawnProcess(self._process,
>                              sipp_args[0],
>                              sipp_args,
>                              {"TERM": "vt100", },
>                              None,
>                              None)
> {code}
> Hence, porting those tests from lua to Python would magifix the problem.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list