Bug 576991 - [test] PartOnTopManagerTest can timeout
Summary: [test] PartOnTopManagerTest can timeout
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.22   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted, test
Depends on:
Blocks:
 
Reported: 2021-11-01 10:24 EDT by Jörg Kubitz CLA
Modified: 2021-11-01 10:24 EDT (History)
0 users

See Also:


Attachments
stacktrace.log (173.53 KB, application/octet-stream)
2021-11-01 10:24 EDT, Jörg Kubitz CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jörg Kubitz CLA 2021-11-01 10:24:02 EDT
Created attachment 287415 [details]
stacktrace.log

The tests from PartOnTopManagerTest running local on windows often get stuck. Logging a lot of errors. Feels like they get stuck in recursive error handling:


!ENTRY org.eclipse.e4.ui.workbench 4 0 2021-11-01 15:14:49.903
!MESSAGE Internal Error
!STACK 0
org.eclipse.e4.core.di.InjectionException: Unable to process "WorkbenchWindow.model": no actual value was found for the argument "MTrimmedWindow".
	at org.eclipse.e4.core.internal.di.InjectorImpl.reportUnresolvedArgument(InjectorImpl.java:478)
	at org.eclipse.e4.core.internal.di.InjectorImpl.resolveRequestorArgs(InjectorImpl.java:469)
...


!ENTRY org.eclipse.jface 4 4 2021-11-01 15:14:49.907
!MESSAGE Internal Error : Internal Error

Reason:
org.eclipse.e4.core.di.InjectionException: Unable to process "WorkbenchWindow.model": no actual value was found for the argument "MTrimmedWindow".
!STACK 0
java.lang.IllegalStateException: Error dialog is supposed to be shown now
	at org.eclipse.e4.ui.internal.workbench.swt.WorkbenchStatusReporter.openDialog(WorkbenchStatusReporter.java:127)
	at org.eclipse.jface.dialogs.ErrorDialog.open(ErrorDialog.java:341)
	at org.eclipse.e4.ui.internal.workbench.swt.WorkbenchStatusReporter.report(WorkbenchStatusReporter.java:65)


logged Stacktraces are way to long to paste it in a bug message.


I got no idea what those tests doing or why they get stuck, but i often see platform ui builds timing out and may be that is related.

Help wanted.