Forum Discussion
EmilyS
14 years agoOccasional Contributor
Hi Dain,
Thanks for your prompt reply.
The tests are run automatically on a scheduled basis by a Team City build agent, which is definitely not running under Antony's account (I've double checked - it runs on a system account). After a bit more digging, I have found that the Java "user.home" for the system account that runs the tests mysteriously changed from "C:\Documents and Settings\Default User" to "C:\Documents and Settings\antony", even though USERPROFILE is still correctly set to "C:\Documents and Settings\Default User".
I have no idea how or why this change has occurred, but can pinpoint it to a 3 hour window yesterday, during which time Antony logged onto the machine that the tests run on and installed some automatic updates. Somehow during this time Java has gotten confused over the user.home directory for the system account that the tests run under.
Here are a few related Java bugs that have been reported.
http://stackoverflow.com/questions/2134 ... g-resolved
http://bugs.sun.com/view_bug.do?bug_id=4787931
Anyway, none of this appears to be directly related to loadui - it appears to be related to either Java itself or some unexplained event on the build machine that the tests run on.
Today I attempted to run loadui from the command line without any system properties passed in, and now it's working again.
--local -p %teamcity.build.workingDir%\LockerLoadTests.xml --reports %teamcity.build.workingDir%\output --format HTML --statistics
Again, I have no idea why it stopped working yesterday and why it's working again now. It had been running for many weeks several times per day without any issues, so it's a bit disconcerting that some unexplained event temporarily confused it!
Thanks,
Emily
Thanks for your prompt reply.
The tests are run automatically on a scheduled basis by a Team City build agent, which is definitely not running under Antony's account (I've double checked - it runs on a system account). After a bit more digging, I have found that the Java "user.home" for the system account that runs the tests mysteriously changed from "C:\Documents and Settings\Default User" to "C:\Documents and Settings\antony", even though USERPROFILE is still correctly set to "C:\Documents and Settings\Default User".
I have no idea how or why this change has occurred, but can pinpoint it to a 3 hour window yesterday, during which time Antony logged onto the machine that the tests run on and installed some automatic updates. Somehow during this time Java has gotten confused over the user.home directory for the system account that the tests run under.
Here are a few related Java bugs that have been reported.
http://stackoverflow.com/questions/2134 ... g-resolved
http://bugs.sun.com/view_bug.do?bug_id=4787931
Anyway, none of this appears to be directly related to loadui - it appears to be related to either Java itself or some unexplained event on the build machine that the tests run on.
Today I attempted to run loadui from the command line without any system properties passed in, and now it's working again.
--local -p %teamcity.build.workingDir%\LockerLoadTests.xml --reports %teamcity.build.workingDir%\output --format HTML --statistics
Again, I have no idea why it stopped working yesterday and why it's working again now. It had been running for many weeks several times per day without any issues, so it's a bit disconcerting that some unexplained event temporarily confused it!
Thanks,
Emily