Hi Paul, On Mon, 2022-01-24 at 00:16 +0100, Abou Al Montacir wrote: > Hi Paul, > > On Sun, 2022-01-02 at 16:30 +0100, Paul Gevers wrote: > > .. > > Moreover CGE upstream think we should abandon armel (and other non > > widely used architectures) as a target for CGE, but I think myself it is > > a good test for the compiler and tend to think we should keep it. > > I agree with you. However, as a Release Team member, I also want to > prevent packages from being out-of-sync for too long. So, what I suggest > in this case is to temporarily disable the test on armel until we have > figured out how to fix the situation. That way the package can migrate > to testing, without making the situation much worse there. > Can you please review [1] before upload? > > [1] > https://salsa.debian.org/pascal-team/castle-game-engine/-/commit/d9b628c179bb53868e3d0bf9adc0b271969a613b Thanks for the review.
I've uploaded with the tests moved to CI and the script executed as expected, but the CI system detects failure. I don't know why as I verified on my machine that the script returns 0 as exit code. It complains about messages on stderr, does it consider writing to stderr as a n error? In that case, is it possible to disable that? The test program is upstream maintained and I don't want to hack in it. -- Cheers, Abou Al Montacir
signature.asc
Description: This is a digitally signed message part
