AtomicRunner: Incorporate the Runner Schedule Order Column # as a execution pointer instead of hostname GUID

[hunty-dumpy]

The current implementation of the runner, adds the current test's GUID to the hostname, and then uses that GUID to know where in the execution schedule it is to continue running.

The Order Column is ignored, this prevents us from executing the same test twice with different input parameters because it creates a loop by "continuing" always from the first time the GUID shows up in the runner schedule csv file.

• Adding the GUID to the hostname is still a very useful feature, although making it optional could be interesting as it would greatly speed up testing since it wouldn't require 2 reboots per test.

[clr2of8]

Hi there, If I understand what you are asking then I think the option to not rename and reboot is included in the Adversary Emulation option where there are no hostname changes and you just pass your schedule on the command line with the -listOfAtomics option.

As a work around for you first issue, you could put another test between the two tests with same guid:

• guidX
• guidA
• guidX
• guidB

Let me know your thoughts. thx