07-19-2017, 08:06 AM
2017/07/18 21:54:25 - Test Created
2017/07/18 21:54:25 - Starting test (initiated by tester SFW10H1105-10.198.69.106)
2017/07/18 21:54:25 - Run 1 assigned to SFW10H1105-10.198.69.106
2017/07/18 21:54:25 - The test was not started but the test job could not be found. Forcing it to end.
2017/07/18 21:54:26 - Run 2 assigned to SFW10H1005-10.198.69.40
2017/07/18 21:54:26 - Run 3 assigned to SFW10H0804-10.198.69.110
2017/07/18 21:54:26 - Run 4 assigned to SFW10H0901-10.198.69.97
2017/07/18 21:54:27 - Run 5 assigned to SFW10H0801-10.198.69.107
2017/07/18 21:55:39 - Test Run Complete. Run: 2, Cached: 0, Done: , Tester: SFW10H1005-10.198.69.40
2017/07/18 21:55:39 - Extracting 5957258 byte uploaded file 'C:\Windows\Temp\php6C66.tmp' to './results/17/07/18/QD/9'
2017/07/18 21:55:40 - Done Processing. Run: 2, Cached: 0, Done: , Tester: SFW10H1005-10.198.69.40
...
2017/07/18 21:57:40 - Marked shard 5 as complete: {"2":true,"1":true,"4":true,"3":true,"5":true}
2017/07/18 21:57:40 - All 5 runs are complete
2017/07/18 21:57:40 - Extracting 6552443 byte uploaded file 'C:\Windows\Temp\php4431.tmp' to './results/17/07/18/QD/9'
2017/07/18 21:57:41 - Done Processing. Run: 5, Cached: 1, Done: 1, Tester: SFW10H0801-10.198.69.107
2017/07/18 21:57:41 - Test Complete
2017/07/18 21:57:41 - Test post-processing complete
I've seen this happen a few times, albeit rarely. Seems to be most prevalent to Edge. I'm still figuring out the code, some sort of error in tests logs, seems like it enters a bad spot in teststatus.inc:
// force the test to end - something went very wrong
Anybody else getting this? I'm going to try to add more test logging to figure it out, just wanted to see if anyone else has run into it.
2017/07/18 21:54:25 - Starting test (initiated by tester SFW10H1105-10.198.69.106)
2017/07/18 21:54:25 - Run 1 assigned to SFW10H1105-10.198.69.106
2017/07/18 21:54:25 - The test was not started but the test job could not be found. Forcing it to end.
2017/07/18 21:54:26 - Run 2 assigned to SFW10H1005-10.198.69.40
2017/07/18 21:54:26 - Run 3 assigned to SFW10H0804-10.198.69.110
2017/07/18 21:54:26 - Run 4 assigned to SFW10H0901-10.198.69.97
2017/07/18 21:54:27 - Run 5 assigned to SFW10H0801-10.198.69.107
2017/07/18 21:55:39 - Test Run Complete. Run: 2, Cached: 0, Done: , Tester: SFW10H1005-10.198.69.40
2017/07/18 21:55:39 - Extracting 5957258 byte uploaded file 'C:\Windows\Temp\php6C66.tmp' to './results/17/07/18/QD/9'
2017/07/18 21:55:40 - Done Processing. Run: 2, Cached: 0, Done: , Tester: SFW10H1005-10.198.69.40
...
2017/07/18 21:57:40 - Marked shard 5 as complete: {"2":true,"1":true,"4":true,"3":true,"5":true}
2017/07/18 21:57:40 - All 5 runs are complete
2017/07/18 21:57:40 - Extracting 6552443 byte uploaded file 'C:\Windows\Temp\php4431.tmp' to './results/17/07/18/QD/9'
2017/07/18 21:57:41 - Done Processing. Run: 5, Cached: 1, Done: 1, Tester: SFW10H0801-10.198.69.107
2017/07/18 21:57:41 - Test Complete
2017/07/18 21:57:41 - Test post-processing complete
I've seen this happen a few times, albeit rarely. Seems to be most prevalent to Edge. I'm still figuring out the code, some sort of error in tests logs, seems like it enters a bad spot in teststatus.inc:
// force the test to end - something went very wrong
Anybody else getting this? I'm going to try to add more test logging to figure it out, just wanted to see if anyone else has run into it.