From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20709 invoked by alias); 24 Jun 2012 14:53:12 -0000 Received: (qmail 20697 invoked by uid 22791); 24 Jun 2012 14:53:11 -0000 X-SWARE-Spam-Status: No, hits=-3.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED,TW_JS X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 24 Jun 2012 14:52:59 +0000 From: "jsm28 at gcc dot gnu.org" To: glibc-bugs@sources.redhat.com Subject: [Bug libc/14233] Many of tst-*.c lack any description of the assertions they test Date: Sun, 24 Jun 2012 14:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jsm28 at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Resolution Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2012-06/txt/msg00239.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=14233 Joseph Myers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #2 from Joseph Myers 2012-06-24 14:52:55 UTC --- As discussed on libc-alpha and now documented at , please take general policy questions and open-ended projects to libc-alpha and the wiki. If there is an objective problem with a test - for example, it has a race condition that may cause it to fail sometimes - then a bug in Bugzilla for the specific issue with the specific test is appropriate. If in doubt about whether the testsuite should be ensuring some particular behavior beyond the relevant standards (where not documented in the glibc manual) then libc-alpha will be the right place to raise such a question about what the glibc API should be (likely resulting in a change to either the manual or the test, or an agreement about which is wrong which could then result in a Bugzilla bug pointing to that agreement). -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.