Hello, Background : I'm currently debugging why my new extended SingleTestFailure including checkBundleStatesDiag() still fails, now that Vratko fixed bug 6523 and Robert merged that (thanks to both of you!), e.g. on genius/features.
I am finding that basically it all boils down to there not being any DOMDataBroker (and his friends) OSGi service being registered... Did something related to this area change recently and things currently just known to be completely badly broken, that badly? Unlikely. If so, is anyone already on this? Or, perhaps are the features definitions in something like genius/features incomplete for such a test to be able to work - would they need to explicitly list some implementation bundle/s which we currently do not (need to)? Or am I maybe making a conceptual mistake... this new test assumes that CSS and BP play nicely together, and wait for each other's deps, so my programmatic "diag" can "prove" that the wiring is fine - am I perhaps missing anything why this couldn't work, in an automated test? (From what I'm seeing so far, I don't think it's just a timing issue... or I'm reading the smoke signs wrong.) I'll continue digging, but wanted to reach out already while digging just on the chance that anyone can jump in with "that's probably because..." kind of idea. Thanks, Michael
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
