| commit | f57723bd1151f9ed3b2b84feb26dd8fdf8027e33 | [log] [tgz] |
|---|---|---|
| author | Marc-Andre Laperle <marc-andre.laperle@ericsson.com> | Sat Feb 13 16:23:01 2016 +0100 |
| committer | Marc-Andre Laperle <marc-andre.laperle@ericsson.com> | Tue Mar 22 11:37:38 2016 -0400 |
| tree | 879e2bdf4dc72b88fbc694cde080a045c7047e5a | |
| parent | 91f9ecc22f55e0a2609ba1640453b262c2d0ae02 [diff] |
tmf: Fix some tests not working in different time zones Also print the timezone at the start of test to help troubleshoot if it happens on a server. Reviewed-on: https://git.eclipse.org/r/66579 This is a combination of 2 commits because the first one introduced a regression and the second fixed it. ---Second commit--- tmf: Fix TestRefreshTextTrace failure because of bad time zone reset Commit 6941941dae56 (https://git.eclipse.org/r/#/c/66579/) changed tests to set explicitly a time zone but it doesn't reset it properly. Because of this, TestRefreshTextTrace had mismatching time stamps. This can reproduced by running FilterViewerTest first then running TestRefreshTextTrace. The easiest way is to modify SWTBotStressTests to have this: s.addTest(new JUnit4TestAdapter(FilterViewerTest.class)); s.addTest(new JUnit4TestAdapter(TestRefreshTextTrace.class)); To fix it, we reset the time zone to the time zone id, not the label. The safest way to do this is to use what we decided to use in the default preference map. Change-Id: I35afe305ac6c81c1ccbb5c01b4031aaa2074e420 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-on: https://git.eclipse.org/r/66723 Reviewed-on: https://git.eclipse.org/r/68881 Reviewed-by: Hudson CI Reviewed-by: Bernd Hufmann <bernd.hufmann@ericsson.com> Tested-by: Bernd Hufmann <bernd.hufmann@ericsson.com> (cherry picked from commit f6612036445d8f438413ac6456a1d9b9abf25fee) Reviewed-on: https://git.eclipse.org/r/68905
This source tree contains the source code for the Trace Compass plugins for Eclipse.
The plugins are categorized as follows:
analysis/ | Generic extensions to the base framework btf/ | Best Trace Format (BTF) integration common/ | Generic utilities that can be used by other plugins ctf/ | Common Trace Format (CTF) reader library doc/ | Documentation and code examples gdbtrace/ | Support for reading and viewing GDB traces lttng/ | LTTng integration pcap/ | libpcap integration rcp/ | Code specific to the RCP version releng/ | Releng-related plugins statesystem/ | State System library tmf/ | Core framework
See the components.svg file for a diagram showing the dependencies between the different components.
To set up the environment to build Trace Compass from within Eclipse, see this wiki page: http://wiki.eclipse.org/Trace_Compass/Development_Environment_Setup
To build the project manually using Maven, simply run the following command from the top-level directory:
mvn clean install
The default command will compile and run the unit tests. Running the tests can take some time, to skip them you can append -Dmaven.test.skip=true to the mvn command:
mvn clean install -Dmaven.test.skip=true
Stand-alone application (RCP) packages will be placed in rcp/org.eclipse.tracecompass.rcp.product/target/products.
The p2 update site, used for installation as plugins inside Eclipse, will be placed in releng/org.eclipse.tracecompass.releng-site/target/repository.
The following Maven profiles, and their corresponding properties, are defined in the build system. You can set them by using -P[profile name] and -D[property name]=[value] in mvn commands.
-Pctf-grammar
Re-compiles the CTF grammar files. This should be enabled if you modify the .g files in the ctf.parser plugin.
-P -build-rcp
Disables the “build-rcp” profile to skip building the RCP archives.
-Pdeploy-rcp
Mainly for use on build servers. Copies the generated RCP archives, as well as the RCP-specific update site, to the paths specified by -DrcpDestination=/absolute/path/to/destination and -DrcpSiteDestination=/absolute/path/to/destination, respectively. Must be used with -Pbuild-rcp!
-Pdeploy-update-site
Mainly for use on build servers. Copies the standard update site (for the Eclipse plugin installation) to the destination specified by -DsiteDestination=/absolute/path/to/destination.
-Psign-update-site
Mainly for use on build servers. Signs all the generated update sites using the Eclipse signing server.
-Pdeploy-doc
Mainly for use on build servers. Copies the generated HTML documentation to the destination specified by -DdocDestination=/absolute/path/to/destination. Some directories may need to already exist at the destination (or Maven will throw related errors).
