369660 – Failures in UITestSuite caused by changes in the test order

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

Bug 369660 - Failures in UITestSuite caused by changes in the test order

Summary: Failures in UITestSuite caused by changes in the test order

Status:	RESOLVED FIXED

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	3.8
Hardware:	All All

Importance:	P3 normal (vote)
Target Milestone:	3.8 M6
Assignee:	Oleg Besedin
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-01-25 08:34 EST by Paul Webster
Modified:	2012-02-07 06:36 EST (History)
CC List:	5 users (show)

See Also:

Attachments
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 Paul Webster

2012-01-25 08:34:57 EST

http://download.eclipse.org/eclipse/downloads/drops/I20120124-2000/testresults/html/org.eclipse.ui.tests_win32.win32.x86_7.0.html#UiTestSuite

We have 4f 2e in the UITestSuite run on windows on java 7.  Oleg, could you please investigate, see if you can reproduce it?

PW

Comment 1 Remy Suen

2012-01-25 09:11:40 EST

The ImportExistingProjectsWizardTest file doesn't look like it's been changed in a while. Will have to do some more digging...

Comment 2 Oleg Besedin

2012-01-25 11:16:55 EST

The failure in ImportExistingProjectsWizardTest is a results of a different order in which tests execute on Java 7. 

Investigating the rest...

Comment 3 Oleg Besedin

2012-01-25 14:04:02 EST

4 out of 6 failures I can duplicate; they are caused by the test run order different from what it was in 1.6. I added test suites that should fix those.

There are two failures that I can not reproduce:
- AdaptableDecoratorTestCase failure in testDisableDecorator
- DecoratorAdaptableTests failure in testNonAdaptableContributions
Those two failures are both in #tearDown() methods. I can not reproduce those locally and there is not much information in the stack traces. There is a good chance that those 2 issues are caused by other tests failing and not cleaning up.

Comment 4 Oleg Besedin

2012-01-25 14:05:50 EST

Changes:

http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?h=R3_development&id=b108d046417d33412665664b0f1ef64bf19d280a

http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?h=R3_development&id=1f2f0853b4381f71acf93ed9f799ee62c5d8a03e

I'll cherry-pick changes over into the Head and will keep this bug open to see the results of the next text run.

Comment 5 Paul Webster

2012-01-25 14:09:42 EST

(In reply to comment #4)
> Changes:
> 
> http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?h=R3_development&id=b108d046417d33412665664b0f1ef64bf19d280a
> 
> http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?h=R3_development&id=1f2f0853b4381f71acf93ed9f799ee62c5d8a03e
> 

Thanx Oleg, I've released these for the 18:00 3.8 build.

PW

Comment 6 Oleg Besedin

2012-01-26 10:41:32 EST

The "old" failures are gone but there is a new test failure in I20120125-1800 in WorkingSetTests#testWorkingSetUpdater(). I can reproduce the failure by changing order test to 
 testWorkingSetWithBasicElementAdapter
 testWorkingSetWithCustomElementAdapter
 testWorkingSetUpdater

Comment 7 Oleg Besedin

2012-01-26 10:51:16 EST

Fixed testWorkingSetUpdater in R3_dev:

http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?h=R3_development&id=ea1a11b8f86624cb1b6adc39bc11e5d3143bc850

Keeping bug open to see the build results.

Comment 8 Dani Megert

2012-02-07 06:36:52 EST

This looks fixed.