|Title||»||Stopping SkylineTester does not abort the second run of SkylineNightly|
|Assigned To||»||Brian Pratt|
Maybe one of your interns could start with this, as it should be pretty simple.
When I click the Stop button in SkylineTester running a nightly test run, you fixed it so that the run does not get posted to the website, but SkylineNightly continues on to the next run, if it was scheduled to run two iterations (e.g. master & release or master & perf)
I find this means that I am now always immediately bringing up Task Manager and finding and killing SkylineNightly in the process list. I would much rather not have to do that, and just have stopping SkylineTester stop the entire SkylineNightly run. If I want anything else to run that day, I will reschedule it, but most often I do this to get some work done on the computer in question, and I just want to be left alone by the testing system for at least the next day or so.