Hi Abou, On 02-01-2022 14:22, Abou Al Montacir wrote:
The issue is that there seem to be a bug in the compiler. However, I'm not able to understand what kind of issue and cloud not produce a small code that triggers it.Moreover, it seems that the bug itself is triggered only when running the full battery of tests. Then the failing test starts to fail. If the test is ran alone (after a machine reboot, or after a while) then it will succeed, but it one runs it after running the full test suite then it will fail systematically.No clue how to go forward and no enough information to open an upstream compiler bug. 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.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
