BUG: Incorrect implementation of program_generator_seed

[brianfu]

When trying to reproduce a violation via tfuzz, we cannot re-generate the same program using the program_generator_seed parameter in the yaml as intended.

For example, if our violation is found after 4822 test programs, using initial program_generator_seed 830819, then our violation-causing program seed should be 830819 + 4822 = 835641. This appears to work as expected (i.e. if we can actually set the seed to 835641, then we will generate the same violating program).

However, when running tfuzz using the same template, if we want to generate this violating program again, we must run with at least -n 2. If our desired seed is 835641, we must set program_generator_seed: 835640 and use -n 2 to (eventually) generate the program with seed 835641.

If we only use -n 1 and program_generator_seed: 835641, then we will not be able to re-generate the same program, likely instead generating the program at seed 835642.

A secondary request would be to insert the program seed into the "Generation Properties" portion of the output report.txt.
Currently, it only shows the given program seed used when launching Revizor, not the seed used to find the violating test case.
If the initial seed is randomized as is default, then the "Program seed" value will show as 0 when output.

[OleksiiOleksenko]

Fixed in the dev branch. Will be merged in the next release.