I had a look at these.
!MESSAGE No IModelProvider exists for project P/TestProject2_1527516764789 of version: EJB Module 3.0
!STACK 0
java.lang.NullPointerException: No IModelProvider exists for project P/TestProject2_1527516764789 of version: EJB Module 3.0
at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProviderManager.java:101)
at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProviderManager.java:281)
at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider.getCachedModelProvider(JEE5ContentProvider.java:76)
at org.eclipse.jst.jee.ui.internal.navigator.Ejb3ContentProvider.getNewContentProviderInstance(Ejb3ContentProvider.java:212)
at org.eclipse.jst.jee.ui.internal.navigator.LoadingJeeDDJob.run(LoadingJeeDDJob.java:50)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
!ENTRY org.eclipse.core.jobs 4 2 2018-05-28 10:14:37.987
!MESSAGE An internal error occurred during: "Loading descriptor for TestProject2_1527516764789.".
!STACK 0
java.lang.NullPointerException
at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider.getCachedModelProvider(JEE5ContentProvider.java:77)
at org.eclipse.jst.jee.ui.internal.navigator.Ejb3ContentProvider.getNewContentProviderInstance(Ejb3ContentProvider.java:212)
at org.eclipse.jst.jee.ui.internal.navigator.LoadingJeeDDJob.run(LoadingJeeDDJob.java:50)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
What looks to be happening is the tests themselves aren't failing. The errors are a result of the Project Explorer view (Common Navigator View) being open in the Java EE perspective and it's refreshing as a result of the tests creating EJB projects. The errors
are introducing a lag in the test run and the number of them is adding up to push the overall test runtime over the 30 minute timeout.
I'm not sure what's caused this to start happening now. These tests are part of a SAP contribution to the project around 9 years ago and they haven't really changed i think since that.
Are the test log files for the earlier
successful builds e.g. #183 maintained? And is it possible to extend the timeout limit for these tests for a test run to see if they pass?