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

  • libjxl: FTBFS because of timeout in test

    From Mathieu Malaterre@21:1/5 to All on Thu Nov 10 08:20:01 2022
    [cc me please]

    Dear hurd porters,

    libjxl is currently in FTBFS state:

    * https://buildd.debian.org/status/fetch.php?pkg=jpeg-xl&arch=hurd-i386&ver=0.7.0-5&stamp=1664979667&raw=0

    libjxl is supposed to build & run on all x86 system out there
    (portable c++ code). Please advise on best solution to work around the
    timeout issue in the (long) running test.

    Thanks& Regards

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Samuel Thibault@21:1/5 to All on Thu Nov 10 10:50:02 2022
    Hello,

    Mathieu Malaterre, le jeu. 10 nov. 2022 08:17:59 +0100, a ecrit:
    libjxl is currently in FTBFS state:

    * https://buildd.debian.org/status/fetch.php?pkg=jpeg-xl&arch=hurd-i386&ver=0.7.0-5&stamp=1664979667&raw=0

    libjxl is supposed to build & run on all x86 system out there
    (portable c++ code). Please advise on best solution to work around the timeout issue in the (long) running test.

    Well, investigation is needed before we can have ideas about what is
    going wrong. You can use the exodar.debian.net porter box to run the problematic test by hand and get a backtrace with gdb.

    With cheers,
    Samuel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mathieu Malaterre@21:1/5 to [email protected] on Tue Nov 15 15:00:01 2022
    Hi,

    On Thu, Nov 10, 2022 at 10:41 AM Samuel Thibault <[email protected]> wrote:

    Hello,

    Mathieu Malaterre, le jeu. 10 nov. 2022 08:17:59 +0100, a ecrit:
    libjxl is currently in FTBFS state:

    * https://buildd.debian.org/status/fetch.php?pkg=jpeg-xl&arch=hurd-i386&ver=0.7.0-5&stamp=1664979667&raw=0

    libjxl is supposed to build & run on all x86 system out there
    (portable c++ code). Please advise on best solution to work around the timeout issue in the (long) running test.

    Well, investigation is needed before we can have ideas about what is
    going wrong. You can use the exodar.debian.net porter box to run the problematic test by hand and get a backtrace with gdb.

    Sorry without strace, I cannot do much:

    * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024141

    Thanks & Regards

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