From: Timerlan Moldobaev <moldobaev@gmail.com>
To: musl@lists.openwall.com
Subject: Re: cluts test suite with musl
Date: Tue, 23 Apr 2013 18:17:15 +0300 [thread overview]
Message-ID: <CAE+eE2KEEKt0XDO=5P8CP2QjC_CvM7rPQYAA-eQTJKaPgNnqZQ@mail.gmail.com> (raw)
In-Reply-To: <20130423134038.GX20323@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
Can you please specify what tests within cluts should work correctly ?
There are chances that in my specific environment some musl issues might
pop up even when running cluts partly.
I can assist in debugging such issues (as it was for testsuite case).
Thanks,
Tim.
On Tue, Apr 23, 2013 at 4:40 PM, Rich Felker <dalias@aerifal.cx> wrote:
> On Tue, Apr 23, 2013 at 03:26:51PM +0300, Timerlan Moldobaev wrote:
> > Hi ,
> >
> > I am trying to run cluts test suite from
> > https://github.com/lmarcetic/cluts over
> > the latest musl libraries.
> > Seems that this test suite is not synchronized with musl as I am
> > getting numerous errors.
> > Is this test suite operational ?
> > Is it a part of musl correct functionality checking ?
> > Can you look at potential issues in musl discovered as a result of cluts
> > tests running ?
>
> I know we don't use all of cluts because some of the tests are wrong,
> and it has some bitrot. Maybe somebody could look into this and making
> an updated version that's correct or at least has the incorrect tests
> disabled? I'll look at it when I have enough time to spend on it.
>
> Rich
>
[-- Attachment #2: Type: text/html, Size: 1814 bytes --]
next prev parent reply other threads:[~2013-04-23 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 12:26 Timerlan Moldobaev
2013-04-23 13:40 ` Rich Felker
2013-04-23 15:17 ` Timerlan Moldobaev [this message]
2013-04-23 15:31 ` Rich Felker
2013-04-23 15:47 ` Rich Felker
2013-04-24 12:26 ` Timerlan Moldobaev
2013-04-24 13:32 ` Rich Felker
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='CAE+eE2KEEKt0XDO=5P8CP2QjC_CvM7rPQYAA-eQTJKaPgNnqZQ@mail.gmail.com' \
--to=moldobaev@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).