https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/ODLPARENT-78 odlparent <p>SingleFeatureTest (SFT) under Karaf 4 never actually fails, even if there are exceptions .. Pax Exam, or (more likely perhaps) something<br/> in that PerRepoTestRunner / PerFeatureRunner wrapper we built, appears to<br/> swallow ll exceptions thrown by SingleFeatureTest's @Test installFeature().</p> <p>Operating System: All<br/> Platform: All</p> ODLPARENT-78

[Karaf 4] SFT never fails, Pax Exam (or our wrappers) swallow all exceptions

Bug Resolved Cannot Reproduce Unassigned Michael Vorburger Tue, 14 Mar 2017 18:27:23 +0000 Wed, 24 Jan 2018 14:27:05 +0000 Fri, 7 Apr 2017 10:39:24 +0000 General 0 3 <p>For the short term, I'll add a try { } catch () </p> { LOG.error(); rethrow } <p> to SFT in <a href="https://git.opendaylight.org/gerrit/#/c/53109/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/53109/</a> - that will at least let us see exceptions in the log...</p> <p>SFT does catch <b>some</b> errors, see for example <a href="https://git.opendaylight.org/gerrit/54077" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/54077</a></p> <p>&gt; SFT does catch <b>some</b> errors</p> <p>Yeah, I was wondering were exactly we were at with this, so I've just re-tested this properly, now that c/53109 is merged (so with a local odlparent already including that change), by simply locally changing features4-test SingleFeatureTest's installFeature() method and removing all of its code, so it actually does not install any feature nor call TestBundleDiag anymore - real simple, and tried to just put these 3 failures into it, one after the other:</p> <p>public void installFeature() throws Exception {<br/> // 1. OK: Assert.fail("boum!"); // AssertionError extends Error<br/> // 2. OK: throw new RuntimeException("boum!");<br/> // 3. OK: throw new Exception("boum!");<br/> }</p> <p>And then tried an e.g. "mvn clean install" this patched features4-test, and then run run "mvn clean package" e.g. in infrautils/common/features/infrautils-features4 - and found that all 3 types do get both logged as as well make mvn fail...</p> <p>So... I'm not sure anymore what exactly I had been smoking and observed 3 weeks ago - but it works now (perhaps related to other changes I made in the final version of c/53109 meanwhile?!).</p> <p>Or maybe there was something particularly strange happening during the featuresService.installFeature and TestBundleDiag, removed for this simplistic test, but I can't think of what - ultimately whatever blows up there would just be some sort of, hopefully, propagated, Exception as above...</p> <p>Let's close this; we can re-open if anyone does observe an SFT with exceptions in the log which does not fail the Maven build when it should... NB it will not be able to detect exceptions thrown in background threads in Karaf, or caught and logged but not propagated exceptions; that's a completely separate problem. Maybe that's actually a particular case that some failures run into; Karaf 4 may well have bugs where certain feature installation problems get logged but do not reach us through the FeaturesService and BundleService we use in SFT to determine if everything installed smoothly?</p> <p>PPS: My local tests confused the hell out of me due to completely unrelated <a href="https://jira.opendaylight.org/browse/ODLPARENT-84" title="Upgrade Pax Exam to solve NoRouteToHostException on Fedora-based Linux due to PAXEXAM-740" class="issue-link" data-issue-key="ODLPARENT-84"><del>ODLPARENT-84</del></a>!</p> Blocks ODLPARENT-81 Development External issue ID 7981 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02367: