On Mon, Feb 08, 2010 at 09:52:32AM -0800, Ian Romanick wrote: | piglit isn't the problem. It's glean and an internal closed-source test | suite that are the problem. We don't have particular control over | either one.
I certainly don't object if you need to modify glean. :-) | Remember the golden rule of testing: anything that isn't tested is | broken. We've had features like that in the past, and every now and | then one sort of visual breaks and goes unnoticed for a long time. One approach that might work for glean is to add a "randomly filter out all but N Visuals" option. Assuming you test frequently enough, each run would be fast, but you could still have confidence that all the Visuals would be tested eventually. Omit the random-filter option when you want to be absolutely sure all the Visuals will be tested. All that aside, your proposal to prune out the less-useful Visuals still sounds like a very good thing to do. Allen ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
