Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324817 - hang? in org.eclipse.wst.common.frameworks.tests.bvt.AutomatedBVT
Summary: hang? in org.eclipse.wst.common.frameworks.tests.bvt.AutomatedBVT
Status: RESOLVED WORKSFORME
Alias: None
Product: WTP Common Tools
Classification: WebTools
Component: wst.common (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: wst.common CLA
QA Contact: Carl Anderson CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-09 00:42 EDT by David Williams CLA
Modified: 2011-07-01 11:50 EDT (History)
0 users

See Also:


Attachments
first thread dump (885.90 KB, text/plain)
2010-09-09 00:42 EDT, David Williams CLA
no flags Details
second thread dump, taken a few minutes later. (885.65 KB, text/plain)
2010-09-09 00:43 EDT, David Williams CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2010-09-09 00:42:41 EDT
Created attachment 178478 [details]
first thread dump

in 3.3 I build circa 9/8/2010

I just happened to notice this unit test suite was "still running" on build machine ... long after the build ended (and all tests should have been killed). 

I believe this would have been from build 

http://build.eclipse.org/webtools/committers/wtp-R3.3.0-I/20100908031241/I-3.3.0-20100908031241/

where the tests did in fact timeout (in the "overall" sense, so would have to dig deep to find any results). 

I'll attach a few thread dumps I snagged. Seems like there was something "running" so not sure it was a true hang, or infinite loop? Or something. 

Just thought I'd provide these stack traces if they are helpful.
Comment 1 David Williams CLA 2010-09-09 00:43:35 EDT
Created attachment 178479 [details]
second thread dump, taken a few minutes later.
Comment 2 Carl Anderson CLA 2011-07-01 11:50:21 EDT
I am just going to close this as WORKSFORME - as far as I know, this has not reoccurred since.  If we see this happening again, we can reopen this bug.