All I can say is: ugh, timeout.rb rearing its ugly head again... :( I don't like the sound of automaticaly installing native gems. This screams "maintenance nightmare" to me (think Windoze). Why don't we leave "SystemTimer not installed" as a fairly visible warning (written to the dashboard, and linked to a documentation page that explains the whole thing, perhaps)? This way, if a build gets stuck, people will easily find out why and take corrective action.
--Alex On Mon, Oct 5, 2009 at 12:16 AM, Chad Woolley <[email protected]>wrote: > Matt Duncan has helped track this down, but the fix will involve the > use of the SystemTimer native gem. I plan to use Bundler to manage > this. Please see the ticket if you'd like to discuss: >
_______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
