<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Tshutdown Goes Live</title>
	<atom:link href="http://alice.nodelman.net/blog/post/tshutdown-goes-live/feed/" rel="self" type="application/rss+xml" />
	<link>http://alice.nodelman.net/blog/post/tshutdown-goes-live/</link>
	<description>infrequent updates and long delays</description>
	<pubDate>Thu, 09 Sep 2010 00:47:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John O&#8217;Duinn&#8217;s Soapbox &#187; Talos now measures shutdown times</title>
		<link>http://alice.nodelman.net/blog/post/tshutdown-goes-live/comment-page-1/#comment-6755</link>
		<dc:creator>John O&#8217;Duinn&#8217;s Soapbox &#187; Talos now measures shutdown times</dc:creator>
		<pubDate>Mon, 04 May 2009 19:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://alice.nodelman.net/blog/?p=75#comment-6755</guid>
		<description>[...] Basically, each Talos test assumed that the previous suite had already ended and exited browser successfully. However, sometimes (usually Vista!), we found that closing a healthy browser took longer then expected. This would cause the next Talos suite to fail out because of the lingering process left by the previous talos suite. This fix should greatly reduce intermittent oranges from Talos in mozilla-central, mozilla-1.9.1 and tracemonkey. In the few days since its been enabled, things look much better already! 2) Users care about shutdown times  Just like we measure startup time, it feels right to measure shutdown time. It was never measured before, but once the idea came up, this felt like a good thing to measure. There are also some edge cases where users exit-and-quickly-restart firefox, which can become unhappy if the browser process is still slowly closing down. The curious can find more details in Alice&#8217;s blogpost here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Basically, each Talos test assumed that the previous suite had already ended and exited browser successfully. However, sometimes (usually Vista!), we found that closing a healthy browser took longer then expected. This would cause the next Talos suite to fail out because of the lingering process left by the previous talos suite. This fix should greatly reduce intermittent oranges from Talos in mozilla-central, mozilla-1.9.1 and tracemonkey. In the few days since its been enabled, things look much better already! 2) Users care about shutdown times  Just like we measure startup time, it feels right to measure shutdown time. It was never measured before, but once the idea came up, this felt like a good thing to measure. There are also some edge cases where users exit-and-quickly-restart firefox, which can become unhappy if the browser process is still slowly closing down. The curious can find more details in Alice&#8217;s blogpost here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
