Open iloveeclipse opened 1 year ago
One thing that strikes me immediately: since when do we have JDT code / bundles during our resources tests???
I would not expect java indexer running, but it is obviously there: org.eclipse.jdt.internal.core.search.processing.JobManager.indexerLoop(JobManager.java:488)
One thing that strikes me immediately: since when do we have JDT code / bundles during our resources tests???
Unlike Tycho which uses only the dependencies, isn't the Eclipse Tester actually running the tests in the whole SDK (so JDT's contributions to CNF are present in that case) ?
One thing that strikes me immediately: since when do we have JDT code / bundles during our resources tests???
Unlike Tycho which uses only the dependencies, isn't the Eclipse Tester actually running the tests in the whole SDK (so JDT's contributions to CNF are present in that case) ?
I think that's exactly it.
Hmm. I don't see anything in the stack that could give a hint why don't we move forward with the test. Could be the thread dump is (consistently) incomplete, I see no stack for
java.lang.Exception: ThreadDump for thread "Notification Thread"
java.lang.Exception: ThreadDump for thread "Signal Dispatcher"
or it could be some thread / job is not started (yet) so we don't see it but test waits for it - however, I don't see where.
See
The first hang dump is :