Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 421323

Summary:	Please restart Hudson's Windows test machine
Product:	Community	Reporter:	David Williams <david_williams>
Component:	CI-Jenkins	Assignee:	CI Admin Inbox <ci.admin-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, webmaster
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows All
Whiteboard:

Description David Williams

2013-11-08 06:31:11 EST

We in platform have been getting many "out of handles" exceptions during our "UI tests" the last few nights ... such as, see 

http://download.eclipse.org/eclipse/downloads/drops4/N20131107-2000/testResults.php

My guess is the machine was just left in a bad state ... perhaps some of our own tests are "left running" in a hung state since the restart the other day? 

In any case, if we still get them after the machine has been rebooted, and restarted as a slave, we'll know to dig deeper on our side. 

Thanks,

Comment 1 Eclipse Webmaster

2013-11-08 09:14:57 EST

I've restarted the Windows slave, there was a 'Java Error - windows is trying to correct the problem' dialog open.

-M.

Comment 2 David Williams

2013-11-08 10:08:17 EST

I'll assumed "fixed". 

I have restarted the unit/integration tests (windows only) for 
N20131107-2000 build. 

If it "messes up" again ... will take more research on our end to figure out if/why they are "crashing windows"! 

To team members who might read this bug, once the tests complete (3 or 4 PM Eastern?) these results will "replace" what ever results are summarized at 
http://download.eclipse.org/eclipse/downloads/drops4/N20131107-2000/testResults.php
so if anyone wants to "save a copy" of failed tests ... you have until then to do so.

Comment 3 David Williams

2013-11-09 15:16:30 EST

FWIW, we've ran tests a couple of times since Windows restarted and no recurrence of "out of handles" and (presumably) no 'Java Error - windows is trying to correct the problem' dialog. So, I'm assuming related to Hudson being restarted (or, vice versa) ... perhaps if easy to automate, when ever Hudson is restarted, Windows should be restarted too? 

In either case, thanks Matt!