1. Forum
  2. Usenet
  3. LINUX.DEBIAN.PORTS.SPARC

  • inetutils 2:2.6-1 FTBFS on buildd sompek

    From Guillem Jover@21:1/5 to All on Wed Feb 26 01:20:02 2025
    Hi!

    I recently uploaded a new inetutils upstream release, which built
    everywhere except on sparc64. I checked the build log and it seems
    to be failing on a test case.

    I tested on stadler.debian.net, and I cannot reproduce it there, so I
    gaveback the build in the hope that perhaps another buildd host would
    be able to take it and pass there, but it has been retried always in
    sompek.

    So as I'm unable to reproduce, this is going to be harder to track
    down, and it's not clear whether there might be something wrong with
    that specific buildd host?

    Thanks,
    Guillem

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Paul Adrian Glaubitz@21:1/5 to Guillem Jover on Wed Feb 26 09:20:01 2025
    Hi Guillem,

    On Wed, 2025-02-26 at 01:11 +0100, Guillem Jover wrote:
    I recently uploaded a new inetutils upstream release, which built
    everywhere except on sparc64. I checked the build log and it seems
    to be failing on a test case.

    I tested on stadler.debian.net, and I cannot reproduce it there, so I gaveback the build in the hope that perhaps another buildd host would
    be able to take it and pass there, but it has been retried always in
    sompek.

    So as I'm unable to reproduce, this is going to be harder to track
    down, and it's not clear whether there might be something wrong with
    that specific buildd host?

    It can be a race condition as SPARC has many cores that are rather slow compared to other architectures. I have looked at the output and I'm not
    sure yet what the exact failure is.

    Adrian

    --
    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer
    `. `' Physicist
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)