id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,difficulty 630,Test scripts that don't properly report exit status,Mario Domenech Goulart,,"The eggs listed bellow don't properly report their exit code to the test infrastructure. Please, make them exit 0 when all tests pass or a non-zero value when one or more tests fail, so salmonella can properly indicate the tests status. Hint: for those using the [http://wiki.call-cc.org/egg/test test egg], you just need {{{(test-exit)}}} at the end of the test script. If you test script relies on errors (or {{{assert}}}) to test egg features, you can assume it is ok (I'm sorry for the false alert), since on error the test script will exit 70 (which is ok for the test infrastructure). I took a look at the last 20 lines of the run.scm files (or at the files they include/load) in the trunk dir for each egg (yeah, it's not exactly a pleasant work). If you don't intend to make a new release of your egg(s) to fix bugs or to add new features soon, please consider making a new release just to fix the tests, so we can have a more accurate idea about the shape of the set of eggs. Also consider that egg tests help to test the compiler too. bindings char-set-literals condition-utils contracts coops-utils couchdb directory-utils discount dsssl-utils elliptic-curves err5rs-arithmetic expand-full fmt format kanren lazy-ffi list-utils logpro lookup-table macosx mailbox mathh modular-arithmetic mw-core mw netstring numspell openal operations packedobjects pandora procedure-decoration progress-indicators quaternoins remote-mailbox ripemd sassy sexp-diff sha2 snowdigest specialized-io srfi-101 srfi-19 srfi-25 srfi-27 srfi-42 srfi-45 stack statistics string-utils sxml-templates symbol-utils synch system tigher-hash tinyclos tuples uuid-ossp xosd yasos yelp",defect,new,major,,extensions,4.7.x,,test infrastructure,,