Hi Julian! On 2024-01-12 01:47, Julian Andres Klode wrote: > Either way, these are harmless
I'm not saying they're harmful, what I'm saying is: 1) the errors you see on armhf when building apt without stack-clash-protection are the same valgrind reports on amd64 as well. Hence, you could consider rebuilding apt without stack-clash-protection on armhf and dropping the armhf conditional in test/integration/test-apt-update-simple 2) if you run valgrind in CI, I think you should probably use --error-exitcode. Otherwise, what's the point of using valgrind at all, if you don't fail when it reports errors? :-) This is not directly relevant to #1060251 of course, I'm happy to file a separate bug against apt if you find that useful.
