Community
Participate
Working Groups
I've been running some tests on the new Windows 7 test box at the foundation and have found that all the jface viewers tests fail. Is this expected or could this be related to a configuration issue on the machine? https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-JUnit/113/testReport/org.eclipse.jface.tests.viewers/
I'll update this with a link to a newer build today once today's test build has completed.
For what its worth, tests pass for me on Windows 7 64 bit.
Here is an updated link from a build I ran on the weekend https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/JUnit- win/lastCompletedBuild/testReport/org.eclipse.jface.tests.viewers/ I couldn't run a hudson build last week because the hudson machines at eclipse kept running out of disk space, thus the delay.
The failing tests rely on the output window being active and visible. Is there a screen saver or something like it installed on the machine?
(In reply to comment #4) > The failing tests rely on the output window being active and visible. Is there > a screen saver or something like it installed on the machine? Kim, ping
Boris, the build user wasn't logged into the machine. Denis has fixed this this morning and I'm running another test build.
So I ran these tests yesterday and have access to the hudson machine to watch them. However, I can't see any Eclipse UI appear on the Hudson machine when the tests are running. So my next step is to run an eclipse installation on that hudson slave via remote desktop and see if the same issue occurs. If not, we know it's an issue with running the tests within Hudson.
So, this is what I've found Run the jface.viewers test via RDP and have the RDP window open on my desktop. The tests pass. Run the test again via hudson or via remote desktop where the remote desktop session is minimized. The tests fail. So I'm not sure what to do. I can show a member of the UI team this behaviour on my machine in you're interested.
I talked to Kim. If we can't get the tests to pass (because they rely on a callback that only happens when the test windows are visible), the only thing we can do is disable them when running on Hudson under Windows. They would still run on the other platforms, so there's hope that they are still valuable.
Boris, we set -Dhudson=true as an Ant property when we run the build on Hudson.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
