On 2026-05-14 17:10:16 +0200, Aurelien Jarno wrote: > Hi, > > On 2026-05-14 15:38, Aurelien Jarno wrote: > > Hi, > > > > On 2026-05-14 12:12, Sebastian Ramacher wrote: > > > Hi > > > > > > On 2026-05-14 11:34:15 +0200, Joël Krähemann wrote: > > > > Hi, > > > > > > > > Please provide more information. Like a stack-trace. What output gives > > > > valgrind on RISCV? > > > > > > The output provided below is from the log of the failing build. If you > > > need additional information, you'll have to ask the porters, request > > > access to a porterbox, or instrument the build to provide additional > > > output if the tests fail. > > > > I have not been able to reproduce the issue on 4 different hosts (all > > with different CPUs), including on the Debian riscv64 porterbox which > > uses the same hardware as the build daemon. I therefore believe it's a > > transient issue. > > > > I therefore gave back the package, let's cross the fingers that the > > build succeed. > > It built successfully, closing the bug.
Thanks for checking. Cheers -- Sebastian Ramacher
