Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365843 - [Unit Test Failure][Ignored]org.eclipse.emf.facet.widgets.nattable.tests.swtbot.Bug344925Test.testBug344925
Summary: [Unit Test Failure][Ignored]org.eclipse.emf.facet.widgets.nattable.tests.swtb...
Status: ASSIGNED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EMF-Facet (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Gregoire Dupe CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 367828
Blocks:
  Show dependency tree
 
Reported: 2011-12-07 04:26 EST by Gregoire Dupe CLA
Modified: 2020-05-01 11:26 EDT (History)
1 user (show)

See Also:
gdupe: juno+
gdupe: kepler+
gdupe: luna+


Attachments
Dumped table model (4.91 KB, application/octet-stream)
2011-12-09 10:50 EST, Gregoire Dupe CLA
gdupe: iplog-
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gregoire Dupe CLA 2011-12-07 04:26:23 EST
Stacktrace

org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.AssertionError: )
	at org.eclipse.swt.SWT.error(SWT.java:4300)
	at org.eclipse.swt.SWT.error(SWT.java:4215)
	at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:196)
	at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)
	at org.eclipse.swt.widgets.Display.syncExec(Display.java:4331)
	at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable.run(UIThreadRunnable.java:76)
	at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable.syncExec(UIThreadRunnable.java:198)
	at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable.syncExec(UIThreadRunnable.java:183)
	at org.eclipse.emf.facet.widgets.nattable.tests.swtbot.Bug344925Test.testBug344925(Bug344925Test.java:209)
Caused by: java.lang.AssertionError: 
	at org.eclipse.emf.facet.widgets.nattable.tests.swtbot.Bug344925Test$3.run(Bug344925Test.java:221)
	at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable$4.doRun(UIThreadRunnable.java:196)
	at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable$1.run(UIThreadRunnable.java:89)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
	at org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication.start(UITestApplication.java:53)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:352)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:624)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:579)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1431)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1407)
	at org.eclipse.core.launcher.Main.main(Main.java:34)
Comment 1 Gregoire Dupe CLA 2011-12-08 15:50:13 EST
I’m not able to reproduce this test failure in my development environment. That’s why I’ve added 2 screen shots in the test.

Committed revision 1255.
Comment 2 Gregoire Dupe CLA 2011-12-09 10:50:16 EST
Created attachment 208170 [details]
Dumped table model

In the revision 1258, I've added a dump of the table model. This table model contains an empty local customization (which is not the expected state).
Comment 3 Gregoire Dupe CLA 2011-12-26 08:20:37 EST
(In reply to comment #2)
> Created attachment 208170 [details]
> Dumped table model
> 
> In the revision 1258, I've added a dump of the table model. This table model
> contains an empty local customization (which is not the expected state).

In this state dump we can see that the localCustomization is empty : 
<localCustomizations metamodelURI="http://www.eclipse.org/emf/2002/Ecore" allQuerySetsAvailable="false"/>

After a column visibility setting, it shouldn't.
Comment 4 Gregoire Dupe CLA 2011-12-26 08:35:58 EST
I've added an exception throw to detect "show/hide" commands which cannot be executed." in org.eclipse.emf.facet.widgets.nattable.internal.NatTableWidget.showHideColumns(List<Column>, List<Column>, boolean).

Committed revision 1415.
Comment 5 Gregoire Dupe CLA 2011-12-27 13:57:10 EST
I can reproduce this failure with a Juno M4 target platform.

I've isolated the problem in the following test class : org.eclipse.emf.facet.widgets.nattable.tests.swtbot.Bug365843

I've ask for help on the EMF forum: http://www.eclipse.org/forums/index.php/mn/msg/270764/1/on/0/?SQ=4c1d009036e7c49e635c7266175fa528
Comment 6 Gregoire Dupe CLA 2012-01-04 06:05:29 EST
(In reply to comment #5)
> I've ask for help on the EMF forum:
> http://www.eclipse.org/forums/index.php/mn/msg/270764/1/on/0/?SQ=4c1d009036e7c49e635c7266175fa528

Ed explained that this is a bug in EMF 2.8. (cf. Bug 367828)
Comment 7 Gregoire Dupe CLA 2013-10-21 11:38:44 EDT
Back to normal in :
 - https://hudson.eclipse.org/hudson/job/emffacet-nightly-maintenance/239/