Hi Pino, Thanks for the well written response. On 25-02-2020 20:41, Pino Toscano wrote: > The test is not flaky. I can see why you say that now, but from my PoV (the release team) it is. >> With a recent upload of gcc-10 to unstable, the autopkgtest of clazy >> failed on arm64 in testing when that autopkgtest was run with the binary >> packages of gcc-10 from unstable. > > The failures have nothing to do with gcc-10. Sorry if it wasn't more clear from the next line that I didn't imply that. > Although, as I said, the issue "fixed itself" until the next > src:llvm-defaults switch, this is slightly less problematic. llvm-defaults and gcc-10 were blocked for some days by the clazy regression on arm64. Can you explain why gcc-10 wasn't blocked by this issue on amd64? Also, the failures on arm64 started before the llvm-defaults upload [1] blocking glibc for some days. Do you also understand that? > In the meanwhile: because of what I said above, I'm demoting the > severity of this bug to important. Also, Paul, please re-enable the > autopkgtest of clazy on ci.debian.net, as they will pass now. I didn't disable the autopkgtest on ci.d.n. I told our migration software (britney) to ignore the regression on arm64. I have removed that hint. Paul [1] https://ci.debian.net/data/autopkgtest/testing/arm64/c/clazy/4223149/log.gz
Attachment:
signature.asc
Description: OpenPGP digital signature