Hi, Sorry, I didn't notice this reply at the time, I did with the recent activity in this bug report.
So, as a belated reply to your earlier efforts, I am writing now to thank you for the effort of looking into this at the time, and sorry for my lack of reply then... and now to the specifics: 2022-12-06 17:15 Benjamin Barenblat:
Control: owner 1025221 ! Control: tags 1025221 - patch Hi, Manuel, Yesterday, I tried a build on a porterbox with your patch. It looks like disabling parallelism improves the situation but does not completely solve it; absl_mutex_test is still flaky. I’ll continue investigating and see if I can get that test fixed. In the meantime, it looks like a recent binNMU to Abseil on riscv64 has passed the buildds. Does that unblock your work?
And to reply to the question, no, when we were in the debian-ports infra it was not a blocker, as we always had the option to disable tests (if need be) and upload to the special suite "unreleased" which allows to have certain changes to the normal building instructions, like disabling tests. Now in the official infra we cannot do that as a last resort, so we're more limited and the packages have to be built "as-is", without any modifications, so as you have seen by the recent pings from other people it is more or a blocker now. As Aurélien and Stephane said, probably makes more sense to make these non-fatal at the moment, like you do in 20230125.3-2 in experimental for mipsel. Not sure if you'd like to go with the current 20220623.1-2 in unstable & testing for the transition, I suppose that by now the upstream version 20230125.3 must be quite stable. In any case we noticed that you joined #debian-riscv IRC channel, so maybe it's best to discuss it there to find the best option for everyone to go forward. Cheers and thanks. -- Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
