<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.7" -->
<rss version="0.92">
<channel>
	<title>happiest unalice ever</title>
	<link>http://alice.nodelman.net/blog</link>
	<description>infrequent updates and long delays</description>
	<lastBuildDate>Thu, 02 Sep 2010 22:43:26 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Talos Documentation Updates</title>
		<description>I recently put some time into updating the talos documentation.  There are now sections describing how numbers are calculated, the history of the tp test along with updates to descriptions of tests, description of talos hardware, where to file bugs and so on.

Any comments and suggestions on what needs ...</description>
		<link>http://alice.nodelman.net/blog/post/talos-documentation-updates/</link>
			</item>
	<item>
		<title>Update to Standalone Talos Yet Again (Now 1.7.1)</title>
		<description>I introduced a not-quite-an-error in 1.7 in that the tests were attempting to load test pages through localhost.  This wouldn't work unless you have a local web server up and working and with the correct document root set.  As Standalone Talos is designed to have minimal requirements I've updated it ...</description>
		<link>http://alice.nodelman.net/blog/post/update-to-standalone-talos-yet-again-now-171/</link>
			</item>
	<item>
		<title>Standalone Talos V1.7</title>
		<description>I've updated Standalone Talos to version 1.7 - available here.  It's been quite a while since a standalone talos update so there are several changes:

	new tscroll test
	updated version of dromaeo
	tests for group opacity perf
	ability to dump all output to stdout using the '--screen' option
	a bunch of orange fixes for failing ...</description>
		<link>http://alice.nodelman.net/blog/post/standalone-talos-v17/</link>
			</item>
	<item>
		<title>Universal Manifest For Unit Tests: A Proposal</title>
		<description>I've come up with a proposed universal manifest format for unit tests based upon the many good comments and suggestions that I received after my last two blog posts.  The simplest case is still very simple and the more complicated cases are now easier to read and understand.  ...</description>
		<link>http://alice.nodelman.net/blog/post/universal-manifest-for-unit-tests-a-proposal/</link>
			</item>
	<item>
		<title>Universal Manifest Format For Unit Tests (part 2)</title>
		<description>There was a lot of good feedback from the post introducing the concept of universal manifest formats for all unit tests.  I want to continue the discussion based upon those questions/comments.

Why aren't we just going to take one of our existing manifest formats and roll it out to the rest ...</description>
		<link>http://alice.nodelman.net/blog/post/universal-manifest-format-for-unit-tests-part-2/</link>
			</item>
	<item>
		<title>Universal Manifest Format For Unit Tests (and maybe Talos)</title>
		<description>Having just joined the Auto-Tools team they thought that they would start me on something fun!  Here's the problem that I was presented with:

	each type of unit test uses it's own manifest file format
	there is a different manifest file reader for each type of manifest
	we hack each manifest separately when ...</description>
		<link>http://alice.nodelman.net/blog/post/universal-manifest-format-for-unit-tests-and-maybe-talos/</link>
			</item>
	<item>
		<title>Standalone Talos V1.5</title>
		<description>In this version:

	Bug 480413 - design test to monitor browser shut down time
	Bug 483097 -  have talos use firefox-bin to run the browser on linux/mac

See Standalone Talos documentation for download and installation instructions. </description>
		<link>http://alice.nodelman.net/blog/post/standalone-talos-v15/</link>
			</item>
	<item>
		<title>Tshutdown Goes Live</title>
		<description>If you've been following along with Bug 480413 -  design test to monitor browser shut down time you'll know that I attempted to roll out Tshutdown on the 18th.  Unfortunately, there were a couple of bugs that weren't discovered in staging and I spent 6 or 7 hours ...</description>
		<link>http://alice.nodelman.net/blog/post/tshutdown-goes-live/</link>
			</item>
	<item>
		<title>Sheriffs Take Notice: We Can Retest Builds With Talos Sendchange</title>
		<description>I'm a little late in posting anything about this, but Bug 468731 -  talos testing of builds using sendchange  is a big deal.  I had initially thought that we wouldn't be able to make use of Buildbot's senchange systems due to the weird hacking that Talos does ...</description>
		<link>http://alice.nodelman.net/blog/post/sheriffs-take-notice-we-can-retest-builds-with-talos-sendchange/</link>
			</item>
	<item>
		<title>Towards Switching To New Graph Server Full Time</title>
		<description>Bug 487329 - Graph server migration tracking is almost fixed and complete.  What does this mean for people who use the graph server?

	graphs-new.mozilla.org will become graphs.mozilla.org
	The current graphs.mozilla.org will become graphs-old.mozilla.org
	No new data will be sent to graphs-old.mozilla.org
	graphs-old.mozilla.org will remain up so that older data can be viewed/searched

We've been ...</description>
		<link>http://alice.nodelman.net/blog/post/towards-switching-to-new-graph-server-full-time/</link>
			</item>
</channel>
</rss>
