It would be helpful for all OpenLaszlo regressions to be annotated with the change number that caused the problem. I wrote a command-line tool to help make this process as painless as possible. Here are the instructions for installing and using this tool:
First, you'll need Ruby installed to run the script. Next, make sure you have a build environment set up. See here for detailed instructions: http://wiki.openlaszlo.org/SubversionBuildInstructions Now cd to a clean branch of the build you want to test and run the binary search tool. Each time a build completes, run your test against the running LPS and see if the problem is still there. Here is some sample output from running the tool: Roboto:trunk maxcarlson$ ruby $LZ_TOOLS_ROOT/svn/binsearch.rb Which revision would you like to start searching from? 8596 Found 10 revisions between 8596 and 8623. Synchronizing and building r8596... Done. Do you still see the problem? (y/n) n Synchronizing and building r8604... Done. Do you still see the problem? (y/n) y Synchronizing and building r8600... Done. Do you still see the problem? (y/n) y Synchronizing and building r8597... Done. Do you still see the problem? (y/n) n r8600 is the revision with the problem: ------------------------------------------------------------------------ r8600 | hqm | 2008-04-09 07:35:20 -0700 (Wed, 09 Apr 2008) | 36 lines ... Once the revision that caused the issue is known, update the JIRA bug with the log produced by binsearch.rb. Thanks, and let me know if you have questions! -- Regards, Max Carlson OpenLaszlo.org
