<?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 for visophyte: shiny? shiny.</title>
	<atom:link href="http://www.visophyte.org/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.visophyte.org/blog</link>
	<description>Andrew Sutherland writes things but (almost) always includes pictures to look at.</description>
	<lastBuildDate>Thu, 31 Mar 2011 20:13:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>Comment on unified JS/C++ backtraces, colorized backtraces, colorized source listing for gdb 7.3/archer-trunk updated by Andrew Sutherland</title>
		<link>http://www.visophyte.org/blog/2011/03/30/unified-jsc-backtraces-colorized-backtraces-colorized-source-listing-for-gdb-7-3archer-trunk-updated/comment-page-1/#comment-4708</link>
		<dc:creator>Andrew Sutherland</dc:creator>
		<pubDate>Thu, 31 Mar 2011 20:13:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=760#comment-4708</guid>
		<description>Neil; I did not know that (or had forgotten if I had :), thank you!

sfink: Yes, x86_64, king of all platforms!  Thanks for pointing out the specific bug number!  I thought I was subscribed to this issue for SpiderMonkey, but apparently I have only been tracking the v8 issue (for node.js needs) and maybe the upstream.</description>
		<content:encoded><![CDATA[<p>Neil; I did not know that (or had forgotten if I had <img src='http://www.visophyte.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> , thank you!</p>
<p>sfink: Yes, x86_64, king of all platforms!  Thanks for pointing out the specific bug number!  I thought I was subscribed to this issue for SpiderMonkey, but apparently I have only been tracking the v8 issue (for node.js needs) and maybe the upstream.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on unified JS/C++ backtraces, colorized backtraces, colorized source listing for gdb 7.3/archer-trunk updated by sfink</title>
		<link>http://www.visophyte.org/blog/2011/03/30/unified-jsc-backtraces-colorized-backtraces-colorized-source-listing-for-gdb-7-3archer-trunk-updated/comment-page-1/#comment-4707</link>
		<dc:creator>sfink</dc:creator>
		<pubDate>Thu, 31 Mar 2011 19:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=760#comment-4707</guid>
		<description>Are you on x86_64? The method JIT preserves the frame pointer, but that&#039;s not good enough for gdb. I&#039;m not sure why. (I know the ABI says that unwinding information is required, but it still ought to be able to fallback to trying to use the frame pointer as it apparently does on x86.)

I am working on the gdb/JIT integration in bug 642320.

And I&#039;m sharpening my axe.</description>
		<content:encoded><![CDATA[<p>Are you on x86_64? The method JIT preserves the frame pointer, but that&#8217;s not good enough for gdb. I&#8217;m not sure why. (I know the ABI says that unwinding information is required, but it still ought to be able to fallback to trying to use the frame pointer as it apparently does on x86.)</p>
<p>I am working on the gdb/JIT integration in bug 642320.</p>
<p>And I&#8217;m sharpening my axe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on unified JS/C++ backtraces, colorized backtraces, colorized source listing for gdb 7.3/archer-trunk updated by Neil Rashbrook</title>
		<link>http://www.visophyte.org/blog/2011/03/30/unified-jsc-backtraces-colorized-backtraces-colorized-source-listing-for-gdb-7-3archer-trunk-updated/comment-page-1/#comment-4705</link>
		<dc:creator>Neil Rashbrook</dc:creator>
		<pubDate>Thu, 31 Mar 2011 10:36:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=760#comment-4705</guid>
		<description>DumpJSStack() got added to release builds too (bug 436495).</description>
		<content:encoded><![CDATA[<p>DumpJSStack() got added to release builds too (bug 436495).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on arbitrarypushlog now more realtimey; likes wide screens, humans by Andrew Sutherland</title>
		<link>http://www.visophyte.org/blog/2011/03/22/arbitrarypushlog-now-more-realtimey-likes-wide-screens-humans/comment-page-1/#comment-4702</link>
		<dc:creator>Andrew Sutherland</dc:creator>
		<pubDate>Wed, 23 Mar 2011 16:33:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=745#comment-4702</guid>
		<description>Oh, you poor, poor, monitor impoverished man. ;)

That should be pretty easy to do, especially if I decrease overall font sizes somewhat.</description>
		<content:encoded><![CDATA[<p>Oh, you poor, poor, monitor impoverished man. <img src='http://www.visophyte.org/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>That should be pretty easy to do, especially if I decrease overall font sizes somewhat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on arbitrarypushlog now more realtimey; likes wide screens, humans by Blake Winton</title>
		<link>http://www.visophyte.org/blog/2011/03/22/arbitrarypushlog-now-more-realtimey-likes-wide-screens-humans/comment-page-1/#comment-4701</link>
		<dc:creator>Blake Winton</dc:creator>
		<pubDate>Wed, 23 Mar 2011 16:28:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=745#comment-4701</guid>
		<description>This is really cool!

Could I get you to change the widescreen width to something less than 1371?  (My MacBook is pretty wide, but apparently 29 pixels too narrow.  :)

Thanks,
Blake.</description>
		<content:encoded><![CDATA[<p>This is really cool!</p>
<p>Could I get you to change the widescreen width to something less than 1371?  (My MacBook is pretty wide, but apparently 29 pixels too narrow.  <img src='http://www.visophyte.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thanks,<br />
Blake.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on arbitrarypushlog now more realtimey; likes wide screens, humans by mcote</title>
		<link>http://www.visophyte.org/blog/2011/03/22/arbitrarypushlog-now-more-realtimey-likes-wide-screens-humans/comment-page-1/#comment-4700</link>
		<dc:creator>mcote</dc:creator>
		<pubDate>Wed, 23 Mar 2011 16:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=745#comment-4700</guid>
		<description>Good stuff!

Links to the newsgroup, google group, and mailing list are here:

https://www.mozilla.org/about/forums/#tools</description>
		<content:encoded><![CDATA[<p>Good stuff!</p>
<p>Links to the newsgroup, google group, and mailing list are here:</p>
<p><a href="https://www.mozilla.org/about/forums/#tools" rel="nofollow">https://www.mozilla.org/about/forums/#tools</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on arbitrarypushlog now more realtimey; likes wide screens, humans by sfink</title>
		<link>http://www.visophyte.org/blog/2011/03/22/arbitrarypushlog-now-more-realtimey-likes-wide-screens-humans/comment-page-1/#comment-4699</link>
		<dc:creator>sfink</dc:creator>
		<pubDate>Wed, 23 Mar 2011 06:55:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=745#comment-4699</guid>
		<description>This latest revision is looking really awesome! Other than some minor bits of functionality, I&#039;d definitely rather use this than tbpl. I have a couple of suggestions, ranging from minor tweaks to major features.

Ok, maybe more than a couple. I was at two dozen a few minutes ago, and have added more since.

So, where did you say was a good place to discuss this, again? mozilla-tools@lists.mozilla.org (newsgroup mozilla.tools) does indeed exist, and appears to be mostly dead. If the automation folks are indeed going to be inventing their own wheel, or taking over yours, then perhaps they could suggest a preferred forum?</description>
		<content:encoded><![CDATA[<p>This latest revision is looking really awesome! Other than some minor bits of functionality, I&#8217;d definitely rather use this than tbpl. I have a couple of suggestions, ranging from minor tweaks to major features.</p>
<p>Ok, maybe more than a couple. I was at two dozen a few minutes ago, and have added more since.</p>
<p>So, where did you say was a good place to discuss this, again? <a href="mailto:mozilla-tools@lists.mozilla.org">mozilla-tools@lists.mozilla.org</a> (newsgroup mozilla.tools) does indeed exist, and appears to be mostly dead. If the automation folks are indeed going to be inventing their own wheel, or taking over yours, then perhaps they could suggest a preferred forum?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on build matrices for arbitrarypushlog by Andrew Sutherland</title>
		<link>http://www.visophyte.org/blog/2011/03/08/build-matrices-for-arbitrarypushlog/comment-page-1/#comment-4684</link>
		<dc:creator>Andrew Sutherland</dc:creator>
		<pubDate>Wed, 09 Mar 2011 18:00:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=732#comment-4684</guid>
		<description>&gt;&gt; although I’m failing to surface some of the details retrieved in the UI
&gt; What exactly are you referring to here?

We discover what the test failures are by scanning the tinderbox logs.  As a result of this scanning, we have more information than just the test that failed.  Especially for mochitests, we have at least one line of the good stuff from &quot;TEST-UNEXPECTED-FAIL &#124; file path &#124; good stuff&quot;.  This would presumably be useful to surface.</description>
		<content:encoded><![CDATA[<p>>> although I’m failing to surface some of the details retrieved in the UI<br />
> What exactly are you referring to here?</p>
<p>We discover what the test failures are by scanning the tinderbox logs.  As a result of this scanning, we have more information than just the test that failed.  Especially for mochitests, we have at least one line of the good stuff from &#8220;TEST-UNEXPECTED-FAIL | file path | good stuff&#8221;.  This would presumably be useful to surface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on build matrices for arbitrarypushlog by Markus Stange</title>
		<link>http://www.visophyte.org/blog/2011/03/08/build-matrices-for-arbitrarypushlog/comment-page-1/#comment-4681</link>
		<dc:creator>Markus Stange</dc:creator>
		<pubDate>Wed, 09 Mar 2011 09:27:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=732#comment-4681</guid>
		<description>Cool stuff!

&gt; although I’m failing to surface some of the details retrieved in the UI

What exactly are you referring to here?</description>
		<content:encoded><![CDATA[<p>Cool stuff!</p>
<p>&gt; although I’m failing to surface some of the details retrieved in the UI</p>
<p>What exactly are you referring to here?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on teaser: Rich contextual information for Thunderbird mozmill failures by visophyte: shiny? shiny. : build matrices for arbitrarypushlog</title>
		<link>http://www.visophyte.org/blog/2011/03/02/teaser-rich-contextual-information-for-thunderbird-mozmill-failures/comment-page-1/#comment-4680</link>
		<dc:creator>visophyte: shiny? shiny. : build matrices for arbitrarypushlog</dc:creator>
		<pubDate>Wed, 09 Mar 2011 04:42:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=722#comment-4680</guid>
		<description>[...] I mentioned in my teaser on rich thunderbird mozmill logs, in order to get the build logs and provide failure clustering you already have to do most of the [...]</description>
		<content:encoded><![CDATA[<p>[...] I mentioned in my teaser on rich thunderbird mozmill logs, in order to get the build logs and provide failure clustering you already have to do most of the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

