Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[tycho-dev] Tycho surefire test output

Hi guys,
I'm having difficulties with troubleshooting test failures due to classloading problems when using tycho surefire plugin.  From what I've seen, the process of running tests involves multiple mechanisms for identifying plugin
dependencies  - maven, p2, equinox, etc. In the end it's not trivial to guess the actual OSGi environment the failing test is run in so the only way to find out what's wrong is to reproduce the problem.
With a dynamic environment as equinox  some classes of problems (unexpected wiring between bundles, missing service dependencies, etc) are not reproducible in all the cases. On the other hand reproducing test failure may
take relatively long time (especially when trying to reproduce/debug the problem in a different environment than it initially occurs).
Instead of reproducing the problem, an offline analysis of the logs could easily help in troubleshooting issues like the mentioned above. Currently tycho log contains some of the required information for such offline analysis:
       - list of the binaries that are installed (and their locations);
       - the command line for launching the java process;
but lack equinox runtime pieces like:
       - the actual wiring and state of the istalled bundles ( e.g "ss" and "b <id>" command output)
       - the list of service components registered in the service registry;
       - the effective set of parameter equinox framework uses;
       - etc.
So my proposal is to add these pieces to tycho logs. Are you interested in a change of that kind?
Thank you,

Back to the top