Nightly testing policy
For your convenience, please check our nightly testing system  --- aka. "TestWeb" --- for the latest status of "your" branch as well as the branch that you forked your branch from and/or you sync your branch with.
Every night, starting from just after 7pm, the system compiles (and tests) each branch that has been modified since the last run on some 20+ platforms. Since testing takes quite some time (up to 5 hours on our slowest machines), only the most "important" branches, i.e., release (-candidate) branches, default branch, and branches that are supposed to be merged into the default development branch soon, are tested; the remaining ones are only compiled. The current list of branches is a follows
compiled & tested:
In case your branch is missing, or your branch is only compiled while you also want it tested, please ask Sjoerd or Stefan.
Modified branches will be tested in the order given above. Testing might be stopped before 9am the next morning, if machines need to be freed for interactive use. In case not all modified branches could be tested by then (or by 7pm the next day), the left over ones will be postponed til the next night.
Please check the TestWeb (of "your" branch) whenever you checked in (i.e., a day later), and fix any compilation or testing errors at your earliest convenience. Our testing system also sends you emails to remind you, in case there where any compilation failures after your checkin. (There are no emails about failing tests; you need to check that yourself.)
Having said that, automatic nightly testing is mainly there to check compilation and testing on other than your primary development platform. We still expect that you do verify the compilation (preferably both in debugging mode and in optimized mode) and run Mtest.py and verify its result on your primary development platform prior to pushing your changes.
In case you have any questions, suggestions, complaints, etc. about our automatic nightly testing systems or Mtest.py, please do not hesitate to contact Sjoerd or Stefan.
In case this is the first time you hear about Mtest.py or our automatic nightly testing system, you should definitely contact Sjoerd or Stefan!
The "Nightly testing" link in the "Ongoing development" section of the left-hand "Overview" panel under http://www.monetdb.org/Home gets you to: