Add support for modification of exe args from test script

[GoogleCodeExporter]

Allow the test script to dynamically modify the exe args.

Original issue reported on code.google.com by de...@battams.ca on 29 Jan 2011 at 7:07

[GoogleCodeExporter]

Any chance of modifying the number of resources consumed in the test script as 
well?

Original comment by robert.d...@gmail.com on 29 Jan 2011 at 8:50

[GoogleCodeExporter]

What would be the use case for that?  Either way, it's not possible because by 
the time the test script is launched, the server's already calculated the 
resource requirements to ensure that it can launch the task to the assigned 
client.  But I'd still like to know why/how you'd use this feature, if it were 
possible. :)

Original comment by de...@battams.ca on 29 Jan 2011 at 9:25

[GoogleCodeExporter]

This issue was closed by revision r1355.

Original comment by de...@battams.ca on 29 Jan 2011 at 10:24

• Changed state: Fixed

[GoogleCodeExporter]

Makes sense about allocation having already taken place.

My use case would be to combine 3 comskip tasks into 1.  I currently have 1 
task for mpeg comskipping that uses 33 resources, 1 for h.264 comskipping that 
uses 67 resources, and a 3rd comskip for a special needs channel (different 
comskip.ini).  Special needs channels could be combined with their respective 
mpeg or h.264 comskip task to limit it to 2 tasks, I just haven't seen to that 
yet.  Currently I have all 3 tasks assigned to new recordings so whichever is 
appropriate will be used and the others will fail in the testing process.  If 
re-allocation of resources was possible all of these could be combined into a 
single comskip task that calls comskip with the appropriate ini file and sets 
the resources as required.

Original comment by robert.d...@gmail.com on 30 Jan 2011 at 1:51

[GoogleCodeExporter]

Hmm... I like that idea, could even use it myself (for basically the same 
reason).  Allow the client to tweak its resource usage at runtime - it's a bit 
of work, but not impossible.  Basically, you'd always start with assigning the 
lowest value to the task and then increase it at runtime as necessary.  When 
the task is completed the resources are reset.  I like it!  Can you open a new 
ticket for this, please?

Original comment by de...@battams.ca on 30 Jan 2011 at 2:36

[GoogleCodeExporter]

Fix verified.

Original comment by de...@battams.ca on 12 May 2011 at 1:36

• Changed state: Verified