Tasks Errors: Tasks stuck in initialized mode
Hi all, We are using TC12.10. Our Master project uses different Tasks and Hosts to run in parralel our UI Desktop Tests (Slave project) on several VMs. We have noticed that some tasks are stuck in the initialized state sometimes. On the Slave machine the UI Tests are running but the Master project is not sync (State of task doesn't change and no log for the tests that were running on the Slave machine) and doesn't know when the tests are completed. That means that at the end of the tests on these VMs, TestExecute's process is still running on the Slave Machine and the Master project is also still running even though all our tests are completed. Does someone ever experienced this issue ? Is there a solution to know when the tests are done on the Slave Machine and to inform the Master project ? Or maybe change the state of the task manually ? We looked into the EventViewer of the VM which was running the task that was stucked in the initialized state. And we noticed this particular event at the same time the tests where running and the task seems to be stucked: Fault bucket , type 0 Event Name: RADAR_PRE_LEAK_WOW64 Response: Not available Cab Id: 0 Problem signature: P1: TestExecute.exe P2: 12.10.590.11 P3: 10.0.14393.2.0.0 P4: P5: P6: P7: P8: P9: P10: Attached files: \\?\C:\Users\MC_QA\AppData\Local\Temp\RDRA4B4.tmp\empty.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA4C5.tmp.WERInternalMetadata.xml These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: a03704c6-1eac-11e7-9c1b-00155d020e41 Report Status: 524384 Hashed bucket: I don't know if this event is related to the issue. It seems that RADAR_PRE_LEAK_WOW64 is a software feature to prevent leaks of memory.Tasks set at running state even when test run is complete
Hi, We have a master project that start our UI tests (slave project with different tests group) on different hosts (VM). We have a task for each VM. We are using TeamCity to start our tests. There is a queue with our UI Tests and after two other project: WebTesting and LoadTests. But sometimes one of thetest group on a VM is complete but the task doesn't come back as idle and stays at running state. This is an issue as TestExecute (running the Master Project) will keep on waiting for all tasks to finish, but since one task is stuck at running state, TestExecute will not stop. Then the other project WebTesting and LoadTests in the queue will not start because TestExecute is still running. Do you have any solution about that ? Why our tasks are staying sometimes on running state after our tests are done ? Thank you for your answers, Camille
