Actually, I'm not 100% sure what happened in this SingelFeatureTest hang. The surefire logs are here: https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/291/archives/sfc/features/features-sfc/target/surefire-reports/org.opendaylight.odlparent.featuretest.SingleFeatureTest-output.txt.gz
They do not contain the usual "Unable to start blueprint container for bundle…" log messages which have been the hallmark of bundle loading deadlock we've been seeing in other instances. This might be a new issue. --Colin On Thu, May 4, 2017 at 7:21 AM, Colin Dixon <[email protected]> wrote: > This isn't an problem with SFC (or rather Is unlikely to be). The problem > with single feature tests hanging is a broader issue spanning projects that > we're still looking into. > > --Colin > > On Thu, May 4, 2017 at 3:22 AM Katie Zhang <[email protected]> > wrote: > >> Hi Brady: >> >> Can you please have someone in your team take a look of this as soon as >> possbile? >> thanks a lot. >> >> Katie >> >> On Wed, May 3, 2017 at 7:04 PM, Colin Dixon <[email protected]> wrote: >> >>> This is another SFT hang. It would really, really, REALLY help if one of >>> the blueprint experts could look at this for a day or two. I'm not sure why >>> these are happening in Carbon, but didn't in Boron. Are the hangs only >>> needs Karaf 4 features? That's a bit hard for me to tell because the >>> feature names are the same, but I could probably figure it out--as could >>> anyone else looking at the Carbon tracking spreadsheet's tab of autorelease >>> failures. If that's the case, is it really all just feature reload issues >>> that would be fixed by adding dependency=true. >>> >>> Anyway, any help would be hugely appreciated. As it stands all we know >>> is that in Carbon, we have a pretty real risk of feature-loading deadlock >>> That appears to be new from Boron. >>> >>> --Colin >>> >>> On Wed, May 3, 2017 at 9:47 PM Jenkins <jenkins-dontreply@ >>> opendaylight.org> wrote: >>> >>>> Attention sfc-devs, >>>> >>>> Autorelease carbon failed to build odl-sfc-ui from sfc in build >>>> 291. Attached is a snippet of the error message related to the >>>> failure that we were able to automatically parse as well as console >>>> logs. >>>> >>>> >>>> Console Logs: >>>> https://logs.opendaylight.org/releng/jenkins092/autorelease- >>>> release-carbon/291 >>>> >>>> Jenkins Build: >>>> https://jenkins.opendaylight.org/releng/job/autorelease- >>>> release-carbon/291/ >>>> >>>> Please review and provide an ETA on when a fix will be available. >>>> >>>> Thanks, >>>> ODL releng/autorelease team >>>> >>>> _______________________________________________ >>>> release mailing list >>>> [email protected] >>>> https://lists.opendaylight.org/mailman/listinfo/release >>>> >>> >>> _______________________________________________ >>> release mailing list >>> [email protected] >>> https://lists.opendaylight.org/mailman/listinfo/release >>> >>> >> >> >> -- >> Bug & Karaf 4 Tracking: >> https://docs.google.com/spreadsheets/d/1VcB12FBiFV4GAEHZSspHBNxKI_ >> 9XugJp-6Qbbw20Omk/edit#gid=921315511 >> >> Steps for Karaf4 Migration >> https://wiki.opendaylight.org/view/Karaf_4_migration >> >> >> Best >> >> katie >> >
_______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
