Factor/To do/Builder
- no e-mail is sent if downloading boot image fails
- if git pull or upload fails, send e-mail; never print errors to the console only
- include benchmark time in report
- subject line should have the cpu/os instead of host name; post host name in report instead
- if 'error', it should say boot error, test error, etc
- if 'report' it should say whether it was clean or not
- if all vocabs load and tests pass, but factor crashes while running benchmarks, builder uploads a binary. this is not good
-
milli-seconds>time, maybe-tail: can be reimplemented using existing words - help lint failures should be release blockers
- clean branch push should be configurable
- should be using
io.files words instead of calling out to rm -rf, cp, etc - uploads may time out
- git operations may time out
- crappy error message if builds directory exists but is empty
- don't delete test-log if factor crashes
- if builder is killed and restarted, it doesn't start a fresh build if there are no git patches available
- compiler errors should be release blockers
- if git pull succeeds and downloading the boot image fails, builder thinks everything is up to date and doesn't build until patches are pushed again
- mac os x dmg should not include
factor, libfactor.dylib in top level, also Factor.app/Contents/Frameworks includes FreeType twice!
This revision created on Sun, 14 Sep 2008 09:10:02 by slava