From: Miroslav Chabrecek <chabrecek@gmail.com>
To: musl@lists.openwall.com
Subject: Testing of musl
Date: Wed, 16 Oct 2019 09:17:24 +0200 [thread overview]
Message-ID: <CAFLg4iDXUp4GJc+msg2dUUm5aqkyug0Q6RXdAsK3Dv7V6OU5dg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hello Everyone,
I tried to run libc-tests (http://nsz.repo.hu/git/?p=libc-test;a=summary)
on x86_64 architecture with musl library.
In results, there are many FAILED tests:
~5 Compilation API errors
~5. Runtime errors
~ 182 Math precision errors
So, I'm asking myself, if I run them in wrong way?
Do you run the test before release and try to have zero failures or what is
the testing process?
Thank you for answering my questions,
Miro
[-- Attachment #2: Type: text/html, Size: 1585 bytes --]
next reply other threads:[~2019-10-16 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 7:17 Miroslav Chabrecek [this message]
2019-10-16 11:44 ` Rich Felker
2019-10-16 13:09 ` Szabolcs Nagy
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=CAFLg4iDXUp4GJc+msg2dUUm5aqkyug0Q6RXdAsK3Dv7V6OU5dg@mail.gmail.com \
--to=chabrecek@gmail.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).