Community
Participate
Working Groups
The permanent VNC connection to the Windows Hudson slave from bug 369873 comment 27 seems to be down since I20130507-1100. This causes at least a test failure in SWT's test_postLorg_eclipse_swt_widgets_Event: It also makes screenshots empty: http://download.eclipse.org/eclipse/downloads/drops4/I20130512-2000/testresults/win32.win32.x86_7.0/org.eclipse.ui.workbench.texteditor.tests.ScreenshotTest.testWindowsTaskManagerScreenshots1.png
We did some work remotely last week that logged out the Hudson use from the console. I've logged that user back in on the console so you should be all set. -M.
Verified in I20130513-2000.
*** Bug 407728 has been marked as a duplicate of this bug. ***
Hudson user is logged out again.
I just checked and it looks like the Hudson user is logged in and the Hudson agent is reporting connected. Are you still seeing otherwise?
(In reply to comment #5) See comment 0. This is about the *UI* session that needs to be open. In I20130520-2000 and I20130521-2000, we had those test failures again.
(In reply to comment #6) > (In reply to comment #5) > See comment 0. This is about the *UI* session that needs to be open. > > In I20130520-2000 and I20130521-2000, we had those test failures again. I talked to Matt and he showed me what was wrong. I was using RDC to check and not the correct VNC session. The VNC session should be okay again.
Thanks, tests are green again in I20130522-2000.
Reopening, issue with VNC connection since I20191125-1800: https://download.eclipse.org/eclipse/downloads/drops4/I20191125-1800/testresults/html/org.eclipse.swt.tests_ep414I-unit-win32-java8_win32.win32.x86_64_8.0.html Note: Windows machine was restarted recently via bug 553456
Hi Mikael/Frederic, Please have a look at the permanent VNC connection on the Windows test m/c. We are still seeing a failing JUnit due to this problem: https://download.eclipse.org/eclipse/downloads/drops4/I20191202-0600/testresults/html/org.eclipse.swt.tests_ep414I-unit-win32-java8_win32.win32.x86_64_8.0.html
This is not an issue with the "permanent VNC connection" on the Windows test machine. The test machine is connected via JNLP and the tests don't need a VNC connection. If there was an issue with the connectivity to the Windows test machine, all tests would fail, not just one. The reference to this bug in the test error message needs to be removed or updated. Since only one of 3891 test cases fails, I'd recommend to check that the test case is still valid.
(In reply to Frederic Gurr from comment #11) > This is not an issue with the "permanent VNC connection" on the Windows test > machine. The test machine is connected via JNLP and the tests don't need a > VNC connection. If there was an issue with the connectivity to the Windows > test machine, all tests would fail, not just one. > > The reference to this bug in the test error message needs to be removed or > updated. > > Since only one of 3891 test cases fails, I'd recommend to check that the > test case is still valid. Ok, but this particular test-case failure is seen only recently after Windows test machine is re-started via bug 553456. Am wondering if something else is needed post machine restart ?
Nothing special is done after machine restart. But the OS updates are managed by Microsoft, could it be a failure with latest Win10 builds?
(In reply to Mikaël Barbero from comment #13) > Nothing special is done after machine restart. But the OS updates are > managed by Microsoft, could it be a failure with latest Win10 builds? Thanks Mikaël, looks like after Win10 machine re-start OS updates got installed. I am able to replicate the issue my side as well, hence closing this bug. Raised bug 553754 to track this.
