Bug 574883 - wait a bit longer before teardown to avoid test errors

If the test fails (it will fail randomly) and we catch that, scheduled
jobs are still running and trigger monitor access like in stack below:

at java.base/java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1043)
at java.base/java.util.ArrayList$Itr.next(ArrayList.java:997)
at org.eclipse.core.tests.runtime.jobs.FussyProgressProvider.sanityCheck(FussyProgressProvider.java:41)
at org.eclipse.core.tests.runtime.jobs.AbstractJobManagerTest.tearDown(AbstractJobManagerTest.java:47)

Change-Id: I83308a48cfae76c11c718d73a0511ce634ffa0e2
Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
Reviewed-on: https://git.eclipse.org/r/c/platform/eclipse.platform.runtime/+/183169
Tested-by: Platform Bot <platform-bot@eclipse.org>
1 file changed
tree: 9b74b6919eca5aa00bc4580872c6a7df33475b39
  1. bundles/
  2. features/
  3. tests/
  4. .gitignore
  7. Jenkinsfile
  10. pom.xml
  11. README.md

Contributing to Eclipse Platform runtime project

Thanks for your interest in this project.

Project description:

Platform runtime provides the background componentns for Eclipse based applications.

Website: https://projects.eclipse.org/projects/eclipse.platform

For more information, refer to the Platform UI wiki page.

How to contribute:

Contributions to Platform UI are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the Platform UI - How to contribute wiki page page on the team wiki.

Test dependencies

Several test plug-ins have a dependency to the Mockito and Hamcrest library. Please install them from the Orbit Download page

Currently the following versions are required:

  • org.hamcrest;bundle-version=“1.3.0”,
  • org.mockito;bundle-version=“2.13”,

How to build on the command line

You need Maven 3.3.1 installed. After this you can run the build via the following command:

mvn clean verify -Pbuild-individual-bundles

Developer resources:

Information regarding source code management, builds, coding standards, and more.

Contributor License Agreement:

Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!


Contact the project developers via the project's “dev” list.


Eclipse Public License (EPL) 2.0