Failure to build elfutils on aarch64

  • Open
  • quality assurance status badge
Details
2 participants
  • Michael Ford
  • Simon Tournier
Owner
unassigned
Submitted by
Michael Ford
Severity
normal
M
M
Michael Ford wrote on 24 Jul 2023 11:34
(address . bug-guix@gnu.org)
CAFyhPjUYndruMBHW=XhTqHwCY+1qFPGwcL7Cc4hBbcHCbPJb+A@mail.gmail.com
Using Guix "guix (GNU Guix) cf9904bcc8dd03e73675475bb4d8746dc434e415"
on and Alpine Linux, aarch64 system,
and calling
"guix build --no-substitutes --check elfutils"
fails with:

============================================================================
Testsuite summary for elfutils 0.187
============================================================================
# TOTAL: 230
# PASS: 220
# SKIP: 8
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0
============================================================================
See tests/test-suite.log
============================================================================
make[3]: *** [Makefile:2577: test-suite.log] Error 1
make[2]: *** [Makefile:2685: check-TESTS] Error 2
make[1]: *** [Makefile:4551: check-am] Error 2
make: *** [Makefile:532: check-recursive] Error 1

Test suite failed, dumping logs.

--- ./tests/test-suite.log --------------------------------------------------

==========================================
elfutils 0.187: tests/test-suite.log
==========================================

# TOTAL: 230
# PASS: 220
# SKIP: 8
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

SKIP: run-large-elf-file.sh
===========================

long_bit: 64
elfclass: 64
space_available: 116
mem_needed: 6
mem_available:
Need at least 6GB free available memory
SKIP run-large-elf-file.sh (exit status: 77)

FAIL: dwfl-bug-fd-leak
======================

./dwfl-bug-fd-leak: dwfl_module_getelf: Callback returned failure
FAIL dwfl-bug-fd-leak (exit status: 2)

SKIP: run-backtrace-data.sh
===========================

/tmp/guix-build-elfutils-0.187.drv-0/elfutils-0.187/tests/backtrace-data:
x86_64 linux only test
SKIP run-backtrace-data.sh (exit status: 77)

FAIL: run-backtrace-dwarf.sh
============================

0xfffff7d8bee0 __pthread_kill_implementation
0xfffff7d499fc raise
0xfffff7d370dc abort
0x4011cc <null>
0x4011cc <null>
0x4011d8 <null>
0x401704 <null>
0xfffff7d37368 __libc_start_call_main
0x401234 <null>
/tmp/guix-build-elfutils-0.187.drv-0/elfutils-0.187/tests/backtrace-dwarf:
dwfl_thread_getframes: Callback returned failure
dwarf: no main
FAIL run-backtrace-dwarf.sh (exit status: 1)

SKIP: run-backtrace-native-biarch.sh
====================================

biarch testing disabled
SKIP run-backtrace-native-biarch.sh (exit status: 77)

SKIP: run-backtrace-native-core.sh
==================================

./backtrace-subr.sh: line 151: flock: command not found
SKIP run-backtrace-native-core.sh (exit status: 77)

SKIP: run-backtrace-native-core-biarch.sh
=========================================

biarch testing disabled
SKIP run-backtrace-native-core-biarch.sh (exit status: 77)

SKIP: run-deleted.sh
====================

SKIP run-deleted.sh (exit status: 77)

SKIP: vdsosyms
==============

SKIP vdsosyms (exit status: 77)

SKIP: run-lfs-symbols.sh
========================

LFS testing is irrelevant on this system
SKIP run-lfs-symbols.sh (exit status: 77)


error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("check" "-j"
"7") exit-status: 2 term-signal: #f stop-signal: #f>
phase `check' failed after 9.0 seconds
command "make" "check" "-j" "7" failed with status 2
S
S
Simon Tournier wrote on 20 Sep 2023 09:04
86pm2d2ulu.fsf@gmail.com
Hi,

On Mon, 24 Jul 2023 at 10:34, Michael Ford <fanquake@gmail.com> wrote:
Toggle quote (6 lines)
> Using Guix "guix (GNU Guix) cf9904bcc8dd03e73675475bb4d8746dc434e415"
> on and Alpine Linux, aarch64 system,
> and calling
> "guix build --no-substitutes --check elfutils"
> fails with:

Thanks for the report.

Using Guix cf9904bcc8dd03e73675475bb4d8746dc434e415 or recent
6113e0529d61df7425f64e30a6bf77f7cfdfe5a5, it seems to build on two build
farms:

Toggle snippet (26 lines)
$ guix weather -s aarch64-linux elfutils
computing 1 package derivations for aarch64-linux...
looking for 2 store items on https://ci.guix.gnu.org...
https://ci.guix.gnu.org ?
100.0% substitutes available (2 out of 2)
at least 1.8 MiB of nars (compressed)
5.6 MiB on disk (uncompressed)
0.090 seconds per request (0.2 seconds in total)
11.1 requests per second

at least 1,000 queued builds
aarch64-linux: 997 (99.7%)
i686-linux: 2 (.2%)
x86_64-linux: 1 (.1%)
'https://ci.guix.gnu.org/api/latestbuilds?nr=1000' returned 500 ("Internal Server Error")

looking for 2 store items on https://bordeaux.guix.gnu.org...
https://bordeaux.guix.gnu.org ?
100.0% substitutes available (2 out of 2)
at least 1.4 MiB of nars (compressed)
5.6 MiB on disk (uncompressed)
0.052 seconds per request (0.1 seconds in total)
19.1 requests per second
(continuous integration information unavailable)

Is it possible that these failures are hardware dependent?

The failures are about:

Toggle snippet (7 lines)
FAIL: dwfl-bug-fd-leak
======================

./dwfl-bug-fd-leak: dwfl_module_getelf: Callback returned failure
FAIL dwfl-bug-fd-leak (exit status: 2)

and

Toggle snippet (19 lines)
FAIL: run-backtrace-dwarf.sh
============================

0xfffff7d8bee0 __pthread_kill_implementation
0xfffff7d499fc raise
0xfffff7d370dc abort
0x4011cc <null>
0x4011cc <null>
0x4011d8 <null>
0x401704 <null>
0xfffff7d37368 __libc_start_call_main
0x401234 <null>
/tmp/guix-build-elfutils-0.187.drv-0/elfutils-0.187/tests/backtrace-dwarf:
dwfl_thread_getframes: Callback returned failure
dwarf: no main
FAIL run-backtrace-dwarf.sh (exit status: 1)


Cheers,
simon
?