• Are there any public ia-64 machines for debugging purposes?

    From Theodore Y. Ts'o@21:1/5 to All on Tue Jul 23 23:30:01 2019
    I need to find an ia64 machine to investigate this build failure:

    https://buildd.debian.org/status/fetch.php?pkg=e2fsprogs&arch=ia64&ver=1.45.3-1&stamp=1563898609&raw=0

    I couldn't find any in the Debian machines list; are there any
    available?

    Failing that, if someone could send me the file
    tests/m_hugefile.failed from the build tree after running "make check"
    on an ia64 machine, that would be really helpful.

    Thanks!!

    - Ted

    P.S. Please explicitly include me on the cc list, as I'm not on the debian-ia64 list.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Paul Adrian Glaubitz@21:1/5 to Theodore Y. Ts'o on Tue Jul 23 23:40:02 2019
    Hi Ted!

    On 7/23/19 11:22 PM, Theodore Y. Ts'o wrote:
    I need to find an ia64 machine to investigate this build failure:

    https://buildd.debian.org/status/fetch.php?pkg=e2fsprogs&arch=ia64&ver=1.45.3-1&stamp=1563898609&raw=0

    I couldn't find any in the Debian machines list; are there any
    available?

    Failing that, if someone could send me the file
    tests/m_hugefile.failed from the build tree after running "make check"
    on an ia64 machine, that would be really helpful.

    We've got a machine that we can create an account on for you. Either
    James can do that or I.

    Setting up a new public ia64 porterbox is on the TODO list but we're
    currently lacking another free machine for that.

    Either way, I need your public OpenSSH key, your desired username and
    both sent in a signed private mail.

    Thanks,
    Adrian

    --
    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer - glaubitz@debian.org
    `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Theodore Y. Ts'o@21:1/5 to John Paul Adrian Glaubitz on Thu Jul 25 21:30:01 2019
    On Tue, Jul 23, 2019 at 11:34:22PM +0200, John Paul Adrian Glaubitz wrote:
    Hi Ted!

    On 7/23/19 11:22 PM, Theodore Y. Ts'o wrote:
    I need to find an ia64 machine to investigate this build failure:

    https://buildd.debian.org/status/fetch.php?pkg=e2fsprogs&arch=ia64&ver=1.45.3-1&stamp=1563898609&raw=0


    Thanks for access. It looks like it works just fine on the machine
    you gave me access. The test in question, m_hugefile, creates a 4T
    file system. Assuming the file system on the build host for /tmp
    supports sparse files, it requires 1.1G of space. If it doesn't
    support sparse files, then it needs 4TB of space:

    % mke2fs -t ext4 -Fq /tmp/foo.img 4T
    % ls -slh /tmp/foo.img
    1.1G -rw-r--r-- 1 tytso tytso 4.0T Jul 25 21:18 /tmp/foo.img

    Is there is a possibility that the problem is the lack of space on
    /tmp on the ia-64 build server?

    Thanks,

    - Ted

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Paul Adrian Glaubitz@21:1/5 to Theodore Y. Ts'o on Thu Jul 25 21:40:01 2019
    Hi Ted!

    On 7/25/19 9:27 PM, Theodore Y. Ts'o wrote:
    Thanks for access. It looks like it works just fine on the machine
    you gave me access. The test in question, m_hugefile, creates a 4T
    file system. Assuming the file system on the build host for /tmp
    supports sparse files, it requires 1.1G of space. If it doesn't
    support sparse files, then it needs 4TB of space:

    % mke2fs -t ext4 -Fq /tmp/foo.img 4T
    % ls -slh /tmp/foo.img
    1.1G -rw-r--r-- 1 tytso tytso 4.0T Jul 25 21:18 /tmp/foo.img

    Thanks for digging into this.

    Is there is a possibility that the problem is the lack of space on
    /tmp on the ia-64 build server?

    /tmp is part of the root file system which has 6.2G of free space,
    it might have been less during the build. I'll see if I can do some
    clean up.

    Adrian

    --
    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer - glaubitz@debian.org
    `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Theodore Y. Ts'o@21:1/5 to John Paul Adrian Glaubitz on Fri Jul 26 00:00:02 2019
    On Thu, Jul 25, 2019 at 09:31:53PM +0200, John Paul Adrian Glaubitz wrote:
    Is there is a possibility that the problem is the lack of space on
    /tmp on the ia-64 build server?

    /tmp is part of the root file system which has 6.2G of free space,
    it might have been less during the build. I'll see if I can do some
    clean up.

    Thanks. I just pushed a new release of e2fsprogs 1.45.3-3. That
    should fix the other build failures on x32 and kfreebsd-*. If the
    clean up fixes the build, then we should be 100% clean on all of the
    Debian ports builds. Otherwise, I can look at skipping m_hugefile
    when running "make check" out of debian/rules.

    - Ted

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Paul Adrian Glaubitz@21:1/5 to Theodore Y. Ts'o on Fri Jul 26 10:50:01 2019
    Hi Ted!

    On 7/25/19 11:56 PM, Theodore Y. Ts'o wrote:
    Thanks. I just pushed a new release of e2fsprogs 1.45.3-3. That
    should fix the other build failures on x32 and kfreebsd-*. If the
    clean up fixes the build, then we should be 100% clean on all of the
    Debian ports builds. Otherwise, I can look at skipping m_hugefile
    when running "make check" out of debian/rules.

    Thanks for the updated package. Unfortunately, you introduced a minor regression with the override for the dh_auto_test target by disabling
    the "nocheck" mechanism [1].

    This means, it's no longer possible to disable the testsuite via environment flags and hence it will be run unconditionally which is a problem on architectures
    like m68k and sh4 where we are currently building the packages with qemu.

    Could you add a nocheck condition around the "make check" call like here [2]?

    Thanks,
    Adrian

    [1] https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=7f4c3bb1200eb727894ddfad6a99167bdf2eb78f
    [2] https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/blob/master/rules#L216

    --
    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer - glaubitz@debian.org
    `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Theodore Y. Ts'o@21:1/5 to All on Sat Jul 27 13:40:02 2019

    Thanks for the updated package. Unfortunately, you introduced a minor regression with the override for the dh_auto_test target by disabling
    the "nocheck" mechanism [1].

    This means, it's no longer possible to disable the testsuite via environment flags and hence it will be run unconditionally which is a problem on architectures
    like m68k and sh4 where we are currently building the packages with qemu.

    Could you add a nocheck condition around the "make check" call like here [2]?

    No problem, I'll fix that in the next upload.

    It looks like m_hugefile failed on x32 still. Is there any chance you
    can send me the debian/BUILD-STD/tests/m_hugefile.failed from the
    build tree, if it was saved after the failed build on the x32 buildd
    servier?

    Thanks,

    - Ted

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