You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tycho surefire VM occasionally fails to terminate for unknown reason and the testing fails with timeout waiting for termination. DumpStackTracesTimer tries to help by revealing the culprit, but fails:
!ENTRY org.eclipse.core.resources 2 10035 2024-06-06 14:59:07.253
!MESSAGE The workspace will exit with unsaved changes in this session.
Exception in thread "DumpStackTracesTimer" java.lang.IllegalArgumentException: Logging bundle must not be null.
at org.eclipse.core.internal.runtime.Log.<init>(Log.java:38)
at org.eclipse.core.internal.runtime.InternalPlatform.getLog(InternalPlatform.java:431)
at org.eclipse.core.runtime.ILog.of(ILog.java:146)
at org.eclipse.core.runtime.Platform.getLog(Platform.java:976)
at org.eclipse.tycho.surefire.osgibooter.DumpStackTracesTimer.log(DumpStackTracesTimer.java:163)
at org.eclipse.tycho.surefire.osgibooter.DumpStackTracesTimer.logWarning(DumpStackTracesTimer.java:154)
at org.eclipse.tycho.surefire.osgibooter.DumpStackTracesTimer.logStackTraces(DumpStackTracesTimer.java:123)
at org.eclipse.tycho.surefire.osgibooter.DumpStackTracesTimer.dump(DumpStackTracesTimer.java:110)
at org.eclipse.tycho.surefire.osgibooter.DumpStackTracesTimer.run(DumpStackTracesTimer.java:95)
at java.base/java.util.TimerThread.mainLoop(Timer.java:566)
at java.base/java.util.TimerThread.run(Timer.java:516)
[ERROR] Timeout of 1500s exceeded. Process was killed
My understanding is that some of my product's background jobs could hang and prevent the shutdown, but I can't come up with a way to catch the situation on build system and DumpStackTracesTimer would be very helpful.
The text was updated successfully, but these errors were encountered:
Environment:
Tycho 4.0.6
Java 21
Tycho surefire VM occasionally fails to terminate for unknown reason and the testing fails with timeout waiting for termination. DumpStackTracesTimer tries to help by revealing the culprit, but fails:
My understanding is that some of my product's background jobs could hang and prevent the shutdown, but I can't come up with a way to catch the situation on build system and DumpStackTracesTimer would be very helpful.
The text was updated successfully, but these errors were encountered: