Re: [cross-project-issues-dev] cbi-papyrus-0.7-nightly build is taking a

[Miles Parker <milesparker@xxxxxxxxx>]

On Sep 30, 2010, at 1:35 PM, Konstantin Komissarchik wrote:

For running tests, you need very little I/O power and good amount of CPU power. Since tests are more likely to fubar a node and thereby cause interference to other jobs, I recommend creating a node/VM per-core as long as memory allows and using only one Hudson executor per node/VM.

This brings up the issue of UI testing. It makes a lot of sense to separate those out. I've got some SWTBot tests that could conceivably take up a lot of time..in fact I have't been putting too much thought into how to get them running hosted just because of potential resource use. Any special recommendations on good strategies for UI?

One other related issue. If a test fails, we probably should't be promoting I'd think -- not even nightly. Has anyone given thought to how this might be accomplished?

-Miles