The deuxdrop messaging experiment‘s current incarnation exists as an (under development) Jetpack that runs in Firefox. I am still trying to shake out functionality to be driven by the UI rather than headless unit tests. While firebug has been a great help, another boon has been the logging framework and log viewing framework developed for [...]
Tagged arbpl, deuxdrop, loggestMy last blog post covered the fancy pants logging being used for the deuxdrop project. To summarize: we have loggers they are organized by ownership hierarchy they provide sufficient metadata that we can reconstruct the loggers that were talking to each other This can result in a lot of loggers. If you look at the [...]
Tagged arbpl, loggestUnderstanding what is going on inside software can be very hard, even for the developers most familiar with the software. During my time working on Thunderbird I used a variety of techniques to try and peer inside: printf/dump/console.log, debuggers, execution analysis (dtrace, chronicle recorder, with object diffs, on timelines), logging (log4j style, with timelines, with [...]
Tagged arbpl, loggestgdb has had integrated python support for some time and it is truly awesome. The innards have changed here and there, so my previous efforts to show colorized/fancy backtraces, show colorized source listings, and provide unified JS/C++ mozilla backtraces (with colors still) have experienced some bit-rot over time. I have de-bitrotted the changes, hard. Hard [...]
Tagged colors!, gaudy, gdb, ShinyArbitrary Pushlog (ArbPL) recap: It shows revision control pushes and the tinderbox build results for specific build trees like tinderboxpushlog (TBPL). It is backed by a server which has a database so your browser is not going to launch a DOS attack on the mozilla infrastructure. On the other hand, if that server falls over… [...]
Tagged arbpl, tbplAs 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 stuff tinderboxpushlog does. One of the key things is summarizing the builds in a way that is useful, where the definition of “useful” probably varies [...]
Tagged arbplSometimes Thunderbird mozmill unit tests fail. When they do, it’s frequently a mystery. My logsploder work helped reduce the mystery for my local mozmill test runs, but did nothing for tinderbox runs or developers without tool fever. Thanks to recent renewed activity on the Thunderbird front-end, this has become more of a problem and so [...]
Tagged arbpl, logging, logsploder, mozmill, node.jsI am doing something where I need to talk to the Mozilla hg pushlog. I noticed things were running disturbingly slow, so I figured I’d look into it. I’m using node.js so htracr (a node.js, libpcap-based via node_pcap http transaction visualizer) seemed like the easiest and most fun way to figure out what is going [...]
Tagged sqliteWhoops. I posted to mozilla.dev.apps.thunderbird about an updated version of logsploder at the end of 2009, but forgot to blog about it. I do so now (briefly) for my own retrospective interest and those who like cropped screenshots. The gloda (global database) tests and various Thunderbird mozmill tests have been augmented for some time (1+ [...]
Tagged log4moz, logging, logsploderI’ve hooked up jstut’s (formerly narscribblus‘) narcissus-based parser and jsctags-based abstract interpreter up to the ajax.org code editor (ace, to be the basis for skywriter, the renamed and somewhat rewritten bespin). Ace’s built-in syntax highlighters are based on the somewhat traditional regex-based state machine pattern and have no deep understanding of JS. The tokenizers have [...]
Tagged ace, bespin, jstut, narcissus, narscribblus, skywriter