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/14358] 2.14.1: many tests failed


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

Andreas Jaeger <aj at suse dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |aj at suse dot de
         Resolution|                            |WONTFIX

--- Comment #2 from Andreas Jaeger <aj at suse dot de> 2012-07-12 12:55:57 UTC ---
Sorry, that's not enough details. Just one comment: Don't use -Wl,--as-needed
for the testsuite.

Version 2.14.1 is old, we're not going to investigate test suite failures from
that version, please check the current 2.16 version.

For glibc 2.16, we have documented known test failures at:
http://sourceware.org/glibc/wiki/Release/2.16

If you have additional failures with glibc 2.16, please file a single report
for each failure after investigating a bit more what fails.

--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-07-12 12:56:02 UTC ---
Also: please make each report for one issue only, not "many" failures.  
Identify what the specific behaviour is that causes a specific test to 
fail on your system but not for other people and file a report describing 
the execution paths through that specific test.  If you find another test 
has a different cause of failure, file a separate bug for it.

-- 
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]