Hello, do any of you know more about why in our ITs the stack traces are wrong?
E.g. this from https://jira.opendaylight.org/browse/NEUTRON-154 : at org.opendaylight.neutron.e2etest.ITNeutronE2E.test_fetch_collection_response(ITNeutronE2E.java:276) at org.opendaylight.neutron.e2etest.ITNeutronE2E.test_fetch_with_one_query_item(ITNeutronE2E.java:296) at org.opendaylight.neutron.e2etest.ITNeutronE2E.test(ITNeutronE2E.java:95) is clearly wrong - that ITNeutronE2E actually calls NeutronNetworkTests and more, but Pax Exam seems to somehow at run-time "inline" it into a single class? I'm assuming there is a good reason why it's doing that (probably class loading by that ad-hoc probe bundle thing), but it's very confusing when you look at such IT test failures... ;-) anyone got any good ideas re. this? More curious - can work around in short-term by ugly copy/paste inlining into single class at source, then stack trace is correctly matching flow as always. Tx, M. -- Michael Vorburger, Red Hat vorbur...@redhat.com | IRC: vorburger @freenode | ~ = http://vorburger.ch
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
