On Fri, 2008-08-15 at 11:57 -0400, Will Coleda wrote: > >> This causes -all- smolder reports to be marked as failures. > > > > Perhaps 'make codetest' or 'make codingstd_tests' should be an automated > > commit hurdle? Meaning, SVN won't allow the commit if those don't pass. > > Assuming we actually want to be running these tests all the time, and > having codingstd violations 'break the build', this is not an > unreasonable approach.[1] > > ISTR our current hosting providers would like to avoid such things, > but that's an understanding from many years ago. > > [1] I don't think that's the way to go.
It seems then that we have two remaining options: 1. Don't run codingstd as part of smolder. 2. Differentiate a codingstd failure and a "real" failure in smolder. Which one of these are you proposing? -'f
