In this case, the sfc failure hit https://jira.opendaylight.org/browse/ODLPARENT-144. That is the weird scr mbean issue that we can't seem to fix and hits us often through different projects.
On Thu, May 31, 2018 at 5:30 PM, Robert Varga <n...@hq.sk> wrote: > On 31/05/18 22:05, Jamo Luhrsen wrote: > > this is exactly one of the reasons it seems to make sense to just disable > > SFT from autorelease. I have no hard data, but I would guess that Brady's > > response below is what we get in the overwhelming majority of these > > failures. > > > > so.... we re-run, cross fingers, hope for a blue build and if we happen > to > > close to a release we magically deem it a candidate and move to the next > > step of validating CSIT. > > This is not specific to SFTs only, this is also true for a number of > other UTs -- let's not forget about that. > > Regards, > Robert > > > _______________________________________________ > release mailing list > rele...@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/release > >
_______________________________________________ sfc-dev mailing list sfc-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/sfc-dev
