On 09/12/12 18:30, CeDeROM wrote: > Uhm, Senior Jenkins complains, but yet I am not able to get into > details on what he is complaining about :-) Help :-) >
You need to check the Jenkins build log for each failure, start with the first in a series, eg. http://openocd.zylin.com/1012 the build log is located http://openocd.zylin.com/jenkins/job/openocd-gerrit/1788/console in this case the issues are related to whitespace, however the commit message does need formatting correctly - see http://openocd.sourceforge.net/doc/doxygen/html/patchguide.html for info you can manually run the same builds script: tools/checkpatch.sh Cheers Spen ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
