Compounding steps debug output

[cevich]

When running a control file with many steps (i.e. 60+) with --verbose, the debugging log contains an entry for every added step that grows each time. After all steps have been added, the number of these extranious lines can needlessly grow into the thousands. For example:

15:45:13 INFO | Initializing job step 1 for subtest uri:
docker/subtests/subexample
15:45:13 DEBUG| Persistent state client.steps now set to [([],
'run_envchecks',
('/home/cevich/devel/test/autotest/client/tests/docker', 'BOFH'), {}),
([], 'run_test',
('/home/cevich/devel/test/autotest/client/tests/docker',
'docker/subtests/subexample', 'test_1-of-35', 600), {})]

...cut add more steps...

15:45:13 DEBUG|
15:45:13 INFO | Initializing job step 35 for subtest uri:
docker/subtests/debug
15:45:13 DEBUG| Persistent state client.steps now set to [([],
'run_envchecks',
('/home/cevich/devel/test/autotest/client/tests/docker', 'BOFH'), {}),
([], 'run_test', ('/home/cevich/devel

...cut 300 more lines of same entry...

/docker', 'docker/subtests/example'), {}), ([], 'run_test',
('/home/cevich/devel/test/autotest/client/tests/docker',
'docker/subtests/debug', 'test_35-of-35', 600), {}), ([],
'run_envchecks',
('/home/cevich/devel/test/autotest/client/tests/docker',
'docker/subtests/debug'), {})] 

[cevich]

@lmr noted:

Well, I'd say to remove it (maybe set a file DEBUG variable to print that if we are so inclined to resolve a bug).