* Akim Demaille wrote on Fri, Mar 20, 2009 at 10:34:19AM CET: > Le 19 mars 09 à 23:17, Ralf Wildenhues a écrit : >> * Jim Meyering wrote on Sat, Mar 14, 2009 at 12:07:15PM CET: >>> Once I taught coreutils' "make check" to tell why a test is skipped, >>> I discovered a few that should not have been skipped. >>> Seeing a summary (and remembering the numbers) might help too. >> >> Yes, I agree. The thing is, though, that there may be an abundance of >> SKIPs; all of which are hopefully not very interesting.[...]
> Maybe putting the logs of the skips last would limit the clutter > sufficiently? Sounds like a good idea; except that if tests do depend on each other, then I would want to see their logs in that order, too. I don't think this can easily be inferred from within the test driver. >> The question is whether there should be a toggle to enable or disable >> logging SKIPs, or they should always be logged, and if a toggle, what >> color that bikeshed^Wtoggle should have. >> >> I take that back. User API questions are never really bike shedding. > > Browsing the result of check-html is nice and it is then easy to go from > one place to another. True. 'less test-suite.log<RET>/^FAIL' of course works too. Maybe this is after all less of a worry for now. Let's see what general feedback on this is if we just keep the summaries. I've pushed this patch to the ad-parallel-tests branch now. Thanks, Ralf
