[Boost-testing] Mitigating --incremental's problems?

From: Beman Dawes (bdawes_at_[hidden])
Date: 2007-10-04 11:52:35

The regression.py --incremental switch is great for those who cycle 
tests often or have a slow machine. But --incremental is imperfect. It 
can cause stale results for a variety of reasons.

In the long run it would be best to fix --incremental's problems. But 
for the short run, perhaps we could mitigate those problems by asking 
testers using --incremental to schedule a job to occasionally delete 
their bin.v2 tree. Say once a week. That wouldn't totally solve 
--incremental's problems, but it might reduce them to a more tolerable 
level.

Another approach would be to build the "once a week" logic right into 
regression.py. That ensures compliance without testers having to do 
anything, but still allows testers to schedule their own bin.v2 removals 
more often if they wish.

Thoughts?

--Beman