Ideally a "smoke test" is (minimum) a matrix of 4 builds of perl (optimisation DEBUGGING, no optimisation) x (unthreaded threaded)
Though for EBCDIC (or any similar rarer platform) I think getting, say, just one build per week, would be something to be happy about. Not ideal for bisecting the culprit when something goes kaboom, but vastly better than nothing.
