On 12/17/25 7:53 AM, Paul Gevers wrote:
On 12/16/25 17:55, Bas Couwenberg wrote:
The CI job needs to be scheduled with doxygen & analizo from unstable to
succeed.
Manually scheduled the combination. For a next time, can you please add a bit
more information of why an action from our is the appropriate solution? I would
have been nice to know from the request that the test had been updated for
different expected results and hence that the test dependency has been
versioned.
I should have linked #1121793 for context.
Our infra once should become smart enough for britney2 to extract that
information, but we currently lack there.
I know, I'm working on that. (#1120799)
This is case is a little different from transitions, there are no removed/new
binaries involved.
I expected that britney would schedule the CI jobs with doxygen & analizo from
unstable already, because it seems to do that when new versions of the affected
source packages are in unstable, just not when only binaries have newer versions in
unstable.
Maybe I should spend time on making britney also consider the results of CI
jobs scheduled by others so we don't have bother you to schedule those.
Kind Regards,
Bas
--
PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
