Hi, On Thu, Jan 29, 2026 at 2:39 PM Paul Gevers <[email protected]> wrote: > > Control: clone -1 -2 > Control: reopen -2 > Control: retitle -2 guile-3.0: segfaults on riscv64 > Control: notfound -2 3.0.10+really3.0.10-6 > Control: found -2 3.0.11-1 > Control: block -1 by -2 > > Ping, but let's split of the segfault bug instead of just mentioning it > in the fails to migrate bug. >
>From the original message, guile-3.0 migrated to testing, which was blocked by guile-fibers and shepherd: ∙ ∙ Autopkgtest for guile-fibers/1.4.2-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass ∙ ∙ Autopkgtest for shepherd/1.0.9-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass I have a simple look at this. Fortunately shepherd[0] got one green light on riscv64 after triggering. For guile-fibers,i t has a chance of failing or passing on hardware of the same specifications. I assume its debci load might be different at different times? In general, it has passed the autopkgtest on more high performance hardware(Sifive P550): https://ci.debian.net/packages/g/guile-fibers/testing/riscv64/68144919/ https://ci.debian.net/packages/g/guile-fibers/testing/riscv64/68131820/ [0]: https://ci.debian.net/packages/s/shepherd/testing/riscv64/ [1]: https://ci.debian.net/packages/g/guile-fibers/testing/riscv64/ BR, Bo
