Google Git
Sign in
eclipse / platform / eclipse.platform.ui / cdcc79741db0732abcb522a44b33c590276344b1
commitcdcc79741db0732abcb522a44b33c590276344b1[log] [tgz]
authorSimeon Andreev <simeon.danailov.andreev@gmail.com>Tue Dec 11 10:34:58 2018 +0100
committerSimeon Andreev <simeon.danailov.andreev@gmail.com>Thu Dec 13 10:23:42 2018 +0100
tree5918cfed4a101356f706ed4b6f7b518e854abf07
parentc6ee3fcc6ae6ce51c7ce2fca1751e86876bfdc7d [diff]
Bug 540222 - All test projects should dump stack traces on timeout

When running tests with org.eclipse.test.EclipseTestRunner during
integration builds, stack traces and screenshots are provided if the
build times out (e.g. due to a hang in the tests). When running test
projects with maven however (e.g. when jdt.debug.tests run in a Gerrit
job), no such stack traces or screenshots are present. Debugging
sporadic hangs in Gerrit jobs is therefore very difficult.

This change is preparation for adding the dumps from EclipseTestRunner
to Gerrit jobs. For this we add the dump functionality at the location
of TestableObject, which is available in plug-ins which define test
applications.

The original code was moved from org.eclipse.test.EclipseTestRunner in
project org.eclipse.test of platform releng, with repository:
https://git.eclipse.org/r/platform/eclipse.platform.releng

The original code is mostly left untouched, aside from using logging
instead of system out and err streams for output.

Change-Id: I194e01de6ba4b7cbdedf4111a48d5f1345240d5d
Signed-off-by: Simeon Andreev <simeon.danailov.andreev@gmail.com>
4 files changed
tree: 5918cfed4a101356f706ed4b6f7b518e854abf07
  1. .mvn/
  2. bundles/
  3. examples/
  4. features/
  5. releng/
  6. tests/
  7. .gitignore
  8. CONTRIBUTING
  9. CONTRIBUTING.md
  10. LICENSE
  11. NOTICE
  12. pom.xml
  13. README.md
README.md

Contributing to Eclipse Platform UI project

Thanks for your interest in this project.

Project description:

Platform UI provides the basic building blocks for user interfaces built with Eclipse.

Some of these form the Eclipse Rich Client Platform (RCP) and can be used for arbitrary rich client applications, while others are specific to the Eclipse IDE. The Platform UI codebase is built on top of the Eclipse Standard Widget Toolkit (SWT), which is developed as an independent project.

Website: http://www.eclipse.org/platform/ui/

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.1.0”,
  • org.mockito;bundle-version=“1.8.4”,

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:

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

License

[Eclipse Public License (EPL) v1.0][4]