Factor/To do/Builder

Fixed:

• 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
• mac os x dmg should not include factor, libfactor.dylib in top level, also Factor.app/Contents/Frameworks includes FreeType twice!
• if load-everything/test-all successful, don't print "Did not pass load-everything: { }"
• compiler errors should be release blockers
• if tests time out, it looks for a tests file and fails
• web app to monitor builder status

To do:

• figure out why SF mailing list manager is blocking build e-mails now
• if builder is killed and restarted, it doesn't start a fresh build if there are no git patches available
• 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
• if fatal error, still report the contents of the logs until that point
• some way to update all builders