Bug Report: Deadlinecommand using args.txt

Deadline
1

Ok this bug is for sure (DL 10.2)

Make a file called c:/temp/args.txt and put these commands in it.

-SetLimitGroup
any_gpu
1000000
""
true

Then run deadlinecommand c:\temp\args.txt

You end up creating a limit group called any_gpu, and a blank member. Click on the allow list members – it will hilight an empty line. It’s strange.

However, if you do the same command from the command line,

deadlinecommand -SetLimitGroup any_gpu 1000000 "" true

you get the correct behaviour and you don’t get that blank member.

2

As I tested the -SetLimitGroup command both the ways as you mentioned above. It showed the same behavior, the Worker Allow list was empty. It is an expected behavior with the command as we are not specifying any worker in the command.

You would need to specify the worker name in the command to add the worker to the Allow list as:

deadlinecommand -SetLimitGroup any_gpu3 1000000 "my_machine" true

Or you can specify to not have the allow list and all the worker to the limit. Run the below command:

deadlinecommand -SetLimitGroup any_gpu4 1000000 * False
3

So I’m looking at your own documentation,

https://docs.thinkboxsoftware.com/products/deadline/10.2/1_User%20Manual/manual/command-line-arguments-pools-groups.html#setlimitgroup

and your example uses double quotes, C:\>deadlinecommand -SetLimitGroup yeti 12 "" False

But the point I am making is that when you issue that command via a single line on the command line, you don’t get that empty group. But if you use args.txt instead, you do get the empty group.

4

Also, I want to create the limit, programmatically, and not add any members to it b/c I will add them later on… which is why I am using the "" option.