On Thu, Mar 16, 2017 at 05:16:48AM -0400, Anders Kaseorg wrote: > On Thu, 16 Mar 2017, Adam Borowski wrote: > > The bug does reproduce for me on _some_ setups, all in regular sbuild: > > > > successful: amd64 > > FTBFS: armhf > > FTBFS: armhf qemu-user on amd64 > > successful: armhf on arm64 > > > > The timezone is the same, so is schroot/sbuild configuration, all what > > differs are architectures and kernel versions. > > > > And it's consistent for repeats. > > Can you show a failing build log?
Looks like I'm an idiot: I did not bother to take a glance at the logs, merely the status line. And it turns out I got two FTBFSes, both different to the original report. The one on armhf/qemu-user is not worth caring about: qemu-user is too buggy for that. The one on real armhf is xsltproc reproducibly dying with SIGBUS. But then, this happens for me but built successfully on buildds. The kernel on my machine is pretty old, lemme give another try getting the incantations for u-boot for recent kernels right... Logs attached, tarred and compressed. -- ⢀⣴⠾⠻⢶⣦⠀ Meow! ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second ⠈⠳⣄⠀⠀⠀⠀ preimage for double rot13!
armhf.logs.tar.xz
Description: application/xz
