This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 222626 - Investigate timing-related JUnit errors in j2ee tests
Summary: Investigate timing-related JUnit errors in j2ee tests
Status: NEW
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Carl Anderson CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-13 13:58 EDT by Carl Anderson CLA
Modified: 2009-03-05 12:32 EST (History)
0 users

See Also:

Attachments
Comment out the two failing test cases for now (1.52 KB, patch)
2008-03-13 14:15 EDT, Carl Anderson CLA 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Carl Anderson CLA 2008-03-13 13:58:45 EDT 
There are two tests that are consistently failing since our Tuesday night drop:

testEAR50_WithDependencies_WithDD
testEAR50_ChangedContentDir_WithDependencies_WithDD

I did some investigation into these, and it appears to be a simple timing problem - the test is trying to verify before the ProjectResourceSet has finished loading due to changes Chuck committed for bug 221565

We will comment out these test cases short term, then investigate either updating the test framework or else updating ProjectResourceSetImpl to allow the demandLoadHelper() to finish before the test case tries to access the EObject.
Comment 1 Carl Anderson CLA 2008-03-13 14:15:22 EDT 
Created attachment 92487 [details]
Comment out the two failing test cases for now

We need to get these two test cases back into the JUnit suite, but for now, we will comment them out.
Comment 2 Carl Anderson CLA 2009-03-05 12:32:24 EST 
Comment on attachment 92487 [details]
Comment out the two failing test cases for now

This patch is "obsolete" since it was applied/committed... need to fix the underlying problem.