We have one single failing CI job left, that is coverity. Is this maybe an issue with respect to authentication to the coverity service? Do we have to do something to activate this in this fork? (Is it maybe an issue because this fork was not made using the GitHub fork mechanism?)
@falko-strenzke Yeah, it should be related to some AUTH token I guess. Should not be relevant, and we would be able to fix it on main repository if needed.
We have one single failing CI job left, that is coverity. Is this maybe an issue with respect to authentication to the coverity service? Do we have to do something to activate this in this fork? (Is it maybe an issue because this fork was not made using the GitHub fork mechanism?)
@ni @TJ-91