On Wed, Apr 9, 2008 at 1:00 PM, thyrsus <[EMAIL PROTECTED]> wrote: > > I merged the trunk into my branch, and it appeared there shouldn't be > any interaction, so I foolishly pushed without doing the unit tests. > I just got 9 failed unit tests. I don't understand them, so it is > conceivable that my code is causing them, but it seems unlikely.
Interesting. By coincidence, I just merged the latest thyrsus branch into ekr-devel. There were no problems with unit tests. However, running all unit tests takes a few seconds *longer* on the ekr-devel branch (containing the thyrsus code) that it does on the trunk! I'm not real happy about that kind of performance. I notice you do some re stuff in getVnode. Are you *sure* this is an improvement? The read code is surprisingly sensitive to what looks like "small" code bits, as various comments attest. I doubt the write code is exercised much. Hmm. I wonder whether setting use_sax = True is skewing the results...I'll have to check. Anyway, how do unit tests work for you with the latest ekr-devel branch? Should I be regularly merging the trunk, or should I just do nothing? Might be a moot point now. See if you can get ekr-devel working. > Here is the command line output - well, wait, dangit, it didn't happen > when I tried to capture the command line output! Unit tests are finicky. I always run them from a console, and leave Leo and the console *strictly* alone while running the tests. The failures you see could be a result of changing focus (say by clicking) during the tests. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
