This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/14233] Many of tst-*.c lack any description of the assertions they test


http://sourceware.org/bugzilla/show_bug.cgi?id=14233

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-06-24 14:52:55 UTC ---
As discussed on libc-alpha and now documented at
<http://sourceware.org/glibc/wiki/Bugzilla%20Procedures>, 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]