On 20/01/2016 14:23, Guillaume Hoffmann wrote: > One way of improving the situation would be to improve the command > "darcs test" itself so that it navigate better in the space of > previous versions. I know that Ganesh has a work-in-progress patch to > enhance Darcs in this way (for instance, Ganesh's work would make > "darcs test" aware of unbuildable states, instead of treating them as > "failing").
This is at http://hub.darcs.net/ganesh/darcs-testtweaks/changes If a test returns exit code 125, it's considered "untestable". test --linear, --bisect and --backoff all take this into account, and now try to find a *sequence* of patches which start with a "success" state and end with a "failed" state, and with only "untestable" states inside the sequence. Once that sequence is found, it then tries to commute out patches from the middle of the sequence to maintain that property but with a shorter sequence of patches. That's based on a heuristic (an exhaustive search would take ages) that roughly amounts to just trying to commute one patch at a time. It's still a bit rough - broken in some edge cases (you probably won't hit those in practice), the progress output is confusing, and the minimisation can't be turned off. Hopefully I'll get it into darcs 2.12. I think the idea of remembering repository states (e.g. "doesn't build") from one run to the next is also very interesting, but I only have vague ideas of how to implement that (perhaps something to do with tagging). Cheers, Ganesh _______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
