Could someone at Kitware have a look at the Windows build machine? There have been no Windows builds for about a week now. Thank you!
I just logged in and took a look at the Task Scheduler in bluestreak. I see the nightly build task wasn’t kicked off from 12/22 until today, with the message “Launch condition not met, user not logged-on”
Looking further into it (but please let me know if anyone immediately knows what caused this, e.g. if it has happened before)
1 Like
Most likely thebuaer eas logged out due to an automatic update. On Cdash you can mark certain builds as “expected” and you can set up email notification for yourself about errors, such as a missing expected build. This could help in detecting and resolving such cases in the future faster.
1 Like
Yeah I am guessing the machine rebooted on Dec 22 for some reason and needed to be logged into, but no one was there to do it at that time. I have done it now so I hope the issue is fixed now.
But I will also try to get the task scheduler settings changed to not require a user to be logged in to avoid this manual step if the machine gets rebooted
On Cdash you can mark certain builds as “expected” and you can set up email notification for yourself about errors, such as a missing expected build. This could help in detecting and resolving such cases in the future faster.
That is useful, thanks I will look into it!
You need a display for tests and it is also easier to detect and fix any errors if you can log on to the interactive session and see for example that a popup is displayed and that’s blocking the workflow.
You could set up auto-login, so that the machine automatically logs in a user after reboot. If the user has limited privileges (e.g., it could be a local user on that computer) then probably there are no security concerns.
2 Likes
Just an update on the nightly windows releases: I know it has been spotty with some days being skipped. I was experimenting with allowing the tasks to run without login, and it resulted in a failure of the nightly task for the last few days because it requires a security policy change that I must wait for our IT to make. They should make that change soon and then I will get to see if this configuration works.
So just a day or two and if it fails again after the change I will revert to the previous working configuration. If it succeeds, then it would be great because we would no longer need to manually log in every time the system reboots.
2 Likes