I have a Linux Master with a Windows (server 2016) Agent. I have several jobs running using the same solution that run perfectly fine. The only difference is the tag name (running SpecFlow) for the run. So one job may run for Italy and and another for Mexico. Italy runs fine, but Mexico fails unless I am looking at the screen when it runs. Keep on mind, the config for both runs is identical other that the directory and the tag.
Some info: Jenkins running as jnlp Running Single thread using Chrome - AutoIt is running due to Windows Auth login for the environment and AutoIT does not support threading. Logged in as admin to the vm - running job as the same user What I am seeing: I have like 8 jobs running (all using AutoIT so this is not the issue). 6 of those jobs run fine. As mentioned, same solution just different tag. Two of the test runs fails and never get past the Windows Auth Login. If I remote into the vm and start the job and watch it, everything works fine. Test cases pass! If I minimize the RDP and look at my local desktop, the tests start failing and are sitting on the login screen. When that I open the RDP window back up and that test case finally fails, the next one begins and runs fine while I watch it. Summary - Test cases fail while I am not directly looking at the VM Desktop for two test runs. I tried running as a service and allowing desktop interaction - no good. Failed again. Job is executed using SpecFlow.Specrun but I have also tried vstestconsole and have the same results. If I run the test from Visual Studio locally or on the Windows vm all is well. Anyone seen this before? Suggestions? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a8200ca9-82f7-471c-bd29-667be1f87808%40googlegroups.com.
