From: Markus B. <Mar...@gm...> - 2006-02-23 22:19:21
|
Christopher Williams wrote: > Markus, > The RDT Nightly Build has been broken for some time now. Can you > take a look at why it's failing the debug test? (While I've done a > lot of checkins, I haven't touched the debugger code or tests, so I > don't know why it suddenly would stop working.) Hi Chris! The build failed with a compile error. Therefore the tests shouldn't have started in the first place. I have to tweak cruise control accordingly. There is another issue: I can't find the files with the compiler errors and warnings. They should be collected and make available in the build report. The log file (go to tab "XML log file" on the cc build results page) is not nice (a nice style sheet would be fitting) but it reveleals the build errors. Just search for ERROR. One of the build erros was inside RubyEditor, the method isNavigationTarget could not be found. It was removed with a check in on feb 10th. Did something go wrong with the synchronisation of your workspace? I've restored some methods (see commit email), could you double check with your changes? There is an error left in RubyCompletionProcessor because of an unresolved import org.eclipse.jface.text.contentassist.TextContentAssistInvocationContext. Is TextContentAssistInvocationContext from the Eclipse 3.2 stream? Markus |