~robcee/ more than just sandwiches

Posted
8 June 2007 @ 9am

Tagged
Code, Testing

What a week

or month, actually… but I’ll try to keep this post limited to the events that occurred most recently.

The background: John Resig did some great work building a new test suite for a recent cut of the MochiKit test suite to run under mochitest (bug #379506). Shaver popped into #developers the other day and said something along the lines of, “could you help John with this review? KTHXBYE” Naturally, I said, sure!

I downloaded the rather lengthy patch and applied it to a pair of trees, did a build and ran runtests.pl. The new tests ran through flawlessly and, seemed ready to go after a quick update to a makefile that was out-of-date. I landed the patch.

And set the tree on fire. (linux, specifically)

LinuxonfireNow a word about case-sensitive (or case-”preserving”) file systems. Mac and Windows (HFS and NTFS respectively) are not really case-sensitive. They will let you put differently-cased characters into file and directory names, and they will show them to you, but they don’t really know the difference between Mochikit and MochiKit.

Not so with Linux’ various UNiXey filesystems.

After excising the error in the Makefile, the redness and swelling cleared and Linux builds started happening again. Unfortunately, and this is where I ask for help, the MochiKit test suite didn’t run on Linux. The only info we had to debug it with was a cryptic:

*** 3605 INFO Running /tests/dom/tests/mochitest/ajax/mochikit/test_Mochikit.html…
*** 3606 ERROR FAIL | Test timed out. |

The MochiKit suite is still in there, merely removed from the Makefile for the time-being until we can figure this out. Astute readers might look at the above filename, and think, “hey, there’s a lower-case ‘k’ in there.” No luck, that’s the filename. I tried increasing the timeout on the tests with the very busy Rob Sayre‘s instructions with no luck. Attempts to run the suite on a local Fedora Core 6 VM provided no help, failing to run MochiKit the first run through, then passing it on a subsequent run.

Apologies to Robert O’Callahan (roc) and the sheriffs for leaving the Linux machines in that state of orangeness overnight.

PS, Lesson learned: Check Linux first.


2 Comments

Posted by
John Resig
8 June 2007 @ 1pm

What a lame situation. I’m working on the new patch-patch right now, I hope to have something later today. I’ll have to pull together a decent Linux testing area, as well. Oof! Thanks for your help.


Posted by
robcee
9 June 2007 @ 10am

yeah, it sucked, but it was my fault for not testing it out on linux before landing it. I learned the hard way. :)

Still appreciate the effort you’ve put into it though. It’ll be great to have this (and Scriptaculous) in our testbed.