El 5 d’abril de 2012 0:51, Steven Chamberlain <[email protected]> ha escrit: > With that patch, tst-timer{4,5} is still failing for me. > > tst-timer4.out: > clock_gettime returned timespec = { 1333577263, 155041665 } > clock_getres returned timespec = { 0, 839 } > > tst-timer5.out: > clock_gettime returned timespec = { 4480, 478115305 } > clock_getres returned timespec = { 0, 839 } > > Oddly, with unpatched eglibc-2.13 I get the same testsuite results > summary that Christoph posted. With timer.diff applied, I get the above > failures and the build hangs at test-clock2.out until I kill it > manually, so I don't get as far as the summary.
tst-timer4 and tst-timer5 are not regressions AFAICT. tst-timer4 should be above the "Encountered regressions" line, and tst-timer5 simply wasn't being run before. As for tst-clock2, are you sure you don't mean tst-timer2? tst-clock2 doesn't use timer_* functions, it's very unlikely for my changes to break it. Is it tagged as regression? We could try to debug these issues as well but if it's only tst-timer4 and tst-timer5 I wouldn't worry for now, as they were already broken before my patch (and we've got more urgent problems atm...). -- Robert Millan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/caofdtxmnuz5wz8yu0rwatkvmasbrksymsgpzym8vdvy1vaz...@mail.gmail.com
