This is the mail archive of the libc-alpha@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]

Re: LSB Test status of glibc 2.18


On Fri, 24 May 2013, Andrey Ponomarenko wrote:

> LSB Core Test (OLVER) result for the oncoming glibc 2.18 on x86/Fedora 18: No
> regressions.
> 
> The glibc became better!
> 
>  * Fixed problems: bug512(tgamma), bug511_1(initstate) and bug803(getdate);
>  * Fixed requirements: math.gamma.tgamma.11.01, math.rand.initstate.11 and
> util.format.time.getdate.{01, 03, 04, 05, 07, 13, 18.01}.
> 
> More info: http://sourceware.org/glibc/wiki/Testing/LSB_Core#Current_results

I still think this would be a lot more useful if each issue said to be a 
glibc bug had a link to the corresponding report in glibc Bugzilla.  (See 
what I said in <http://sourceware.org/ml/libc-alpha/2013-01/msg01016.html> 
regarding reopening bugs that were wrongly closed, tracing requirements 
back to POSIX and ISO C, etc.)

Some of those bugs may already be filed, but others may need filing (or 
reopening).  And in any case, whatever produces the test descriptions in 
these LSB reports needs to be updated to refer to the glibc bugs (or as 
applicable, upstream bug reports for other system components in which LSB 
is detecting bugs).

-- 
Joseph S. Myers
joseph@codesourcery.com


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