public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/30015] New: tst-audit24* failures on sparc64-unknown-linux-gnu (Didn't expect signal from child: got `Illegal instruction')
Date: Tue, 17 Jan 2023 19:13:19 +0000	[thread overview]
Message-ID: <bug-30015-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30015

            Bug ID: 30015
           Summary: tst-audit24* failures on sparc64-unknown-linux-gnu
                    (Didn't expect signal from child: got `Illegal
                    instruction')
           Product: glibc
           Version: 2.37
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: sam at gentoo dot org
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---
              Host: sparc64-unknown-linux-gnu
            Target: sparc64-unknown-linux-gnu
             Build: sparc64-unknown-linux-gnu

We've added glibc to the new gentoo-sparc CI builder on builder.sourceware.org.
For glibc, we get the following on master from make check
(https://builder.sourceware.org/buildbot/#/builders/232/builds/9/steps/5/logs/stdio):
```
FAIL: elf/tst-audit24a
FAIL: elf/tst-audit24b
FAIL: elf/tst-audit24c
FAIL: elf/tst-audit24d
UNSUPPORTED: elf/tst-env-setuid
UNSUPPORTED: elf/tst-env-setuid-tunables
FAIL: elf/tst-pldd
XPASS: elf/tst-protected1a
XPASS: elf/tst-protected1b
UNSUPPORTED: elf/tst-valgrind-smoke
      5 FAIL
    310 PASS
      3 UNSUPPORTED
      1 XFAIL
      2 XPASS
```

The various elf/tst-audit24*.out files are all the same, e.g. from
https://builder.sourceware.org/testrun/c3e80401785b4c75be4728a8f4d6fca63cfd70cd?filename=elf%2Ftst-audit24a.out:
```
Didn't expect signal from child: got `Illegal instruction'
```

tst-pldd looks like a different failure so I'll file a another bug for that.
Access to this environment is available via SSH on request, just email me an
SSH key. It's a clean environment used only for CI.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-01-17 19:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 19:13 sam at gentoo dot org [this message]
2024-01-17 12:54 ` [Bug libc/30015] " adhemerval.zanella at linaro dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30015-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).