Test all RTBC and CNR issues on rotation
catch - September 16, 2008 - 01:25
| Project: | Test driven development infrastructure |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
It seems like drupaltestbedbot only tests patches when they've been uploaded recently. To keep the queues short, it should also go through the whole needs review and rtbc queue in sequence, over and over, since many patches that passed once, may cease to apply as soon as there's a commit. This will be one of the big wins in terms of reducing man hours spent testing broken patches.
#1
well it's sort of doing that: #307197: Testing the incorrect patch posting multiple comments.
;)
#2
That's not quite what I had in mind :(
Retitled to make it more obvious. The idea is - if a patch passes one day, it might not the next, so we should loop through all RTBC and CNR issues on an ongoing basis. I don't think it matters too much if new issues get neglected by the testing bot for a few days, since as we clear out failing patches, the queues will get shorter anyway, and less lag.
#3
Should be doing that now....confirmed as it just started to re-send after 72 hours. (not enough slaves to go faster at this point)
#4
Automatically closed -- issue fixed for two weeks with no activity.