No, I don’t think that would work – it insists on figuring out what type of terminal it has, and if it’s unknown it dies. We could ask the maintainer to fix SIPp >;->

From: Andy Caldwell [mailto:notifications@github.com]
Sent: 08 May 2013 16:28
To: Metaswitch/clearwater-live-test
Cc: Keith Wansbrough
Subject: Re: [clearwater-live-test] [Reviewer: Andy] Enhance live test (#4)


In lib/test-definition.rb:

> @@ -184,7 +188,7 @@ def launch_sipp

>      @deployment = ENV['PROXY'] if ENV['PROXY']

>      transport_flag = { udp: "u1", tcp: "t1" }[@transport]

>

> -    @sipp_pid = Process.spawn("sudo ./sipp -m 1 -t #{transport_flag} --trace_msg --trace_err -max_socket 100 -sf \"#{@scenario_file}\" #{@deployment}",

> +    @sipp_pid = Process.spawn("sudo TERM=xterm ./sipp -m 1 -t #{transport_flag} --trace_msg --trace_err -max_socket 100 -sf \"#{@scenario_file}\" #{@deployment}",

Could you also do this by setting :in => "/dev/null" in the options hash? Maybe SIPp just terminates if it reads EOF from the stdin... that would be sad.

—
Reply to this email directly or view it on GitHub<https://github.com/Metaswitch/clearwater-live-test/pull/4/files#r4136269>.