public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: binutils@sourceware.org
Cc: Sam James <sam@gentoo.org>
Subject: New sourceware binutils-gentoo-sparc builders
Date: Sat, 14 Jan 2023 22:02:17 +0100	[thread overview]
Message-ID: <20230114210217.GA6963@gnu.wildebeest.org> (raw)

Hi,

Thanks to Sam James, the Gentoo Foundation and OSUOSL
builder.sourceware.org now has a gentoo-sparc worker [1]
which runs binutils CI [2] and try [3] builders.

It seems in good shape with only two unexpected failures for
the ld tests:

   	 === gas Summary ===

# of expected passes		365
# of unsupported tests		7


     === binutils Summary ===

# of expected passes		253
# of unsupported tests		6

     === libsframe Summary ===

# of expected passes		23

     === libctf Summary ===

# of expected passes		18

     === ld Summary ===

# of expected passes		1596
# of unexpected failures	2
# of expected failures		26
# of untested testcases		1
# of unsupported tests		157

The two ld FAILS are:

Running: tmpdir/pr26391-5 > tmpdir/pr26391-5.out
child killed: illegal instruction
FAIL: Run pr26391-5

Running: tmpdir/pr26391-6 > tmpdir/pr26391-6.out
child killed: illegal instruction
FAIL: Run pr26391-6

Hopefully Sam can help figure out what caused the crash.

Cheers,

Mark

[1] https://builder.sourceware.org/buildbot/#/workers/35
[2] https://builder.sourceware.org/buildbot/#/builders?tags=binutils
[3] https://sourceware.org/binutils/wiki/Buildbot

             reply	other threads:[~2023-01-14 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 21:02 Mark Wielaard [this message]
2023-01-14 21:34 ` Sam James
2023-01-15  0:22   ` John Paul Adrian Glaubitz
2023-01-15  0:52     ` Sam James

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=20230114210217.GA6963@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=sam@gentoo.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).