GUI unit tests only work when logged in over RDP

Hi,

We're having trouble running our GUI tests which require a SDL window on the unstable OS. SDL basically errors out that it cannot find a display (e.g. https://ci.appveyor.com/project/matham/kivy/build/1.0.242/job/ngj8e1j71gli0efw#L2406). However, if I log in using RDP, the tests will work and it manages to create a window.

I'm not quite sure what the solution is, if any since I don't fully understand the windows sessions. But I'd guess that the basic session is a console session which has no display? Or is it that it's not auto logging in and it needs to be set to auto log in? I have seen http://help.appveyor.com/discussions/questions/678-gui-unit-testing-in-appveyor, and as I said tried with unstable which doesn't fix it.

http://stackoverflow.com/questions/19441324/how-to-run-gui-tests-on-a-jenkins-windows-slave-without-remote-desktop-connectio seems to imply that it's a problem with the user not logging in by default. I tried net user setting appveyor to active but it made no difference. I even tried to cheat by making appveyor start a rdp session to itself (https://ci.appveyor.com/project/matham/kivy/build/1.0.237/job/tgcvakwye51v8p0h#L12), but unsurprisingly that didn't work.

At this point I'm at a loss for what to do?

  1. Thanks, that's awesome! That solves the issue. I guess I got the ip wrong when I tried the rdp to itself solution.

  2. matham closed this discussion on 09 Jan, 2016 09:00 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac