From: Ben Woodard <woodard@redhat.com>
To: libabigail@sourceware.org
Subject: 1.0 RC Test results All known bugs are in
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <96C5067E-320C-4A63-93EC-0BCB3E0F6514@redhat.com> (raw)
I spent the morning going through the results of yesterday’s big run. All known bugs are in. Unless I missed something hidden in the noise or two bugs that look like the same problem to me, I think that even the early results picked up everything.
19434 19433 - these both seem to be remaining issues with proper escaping of values in the DWARF. I think that you fixed some of these but these two problems still exist.
19204 looks like a problem with the DWARF reader
19141 19142 looks like problems in handling the ELF from and binaries.
19138 is the biggy. This is by far the most common problem. It triggers 10x more than all the other issues combined. I would say that just fixing this bug would increase the signal to noise ratio in detecting problems monumentally.
next reply other threads:[~2016-01-07 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 Ben Woodard [this message]
2016-01-01 0:00 ` Dodji Seketeli
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=96C5067E-320C-4A63-93EC-0BCB3E0F6514@redhat.com \
--to=woodard@redhat.com \
--cc=libabigail@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).