On 09 Nov 2012, at 18:46, Stijn De Weirdt wrote: > i was never very happy with this option since it gives the user the illusion > that it will always work, which ofcourse is impossible (similar to some of > the other --try- options). > it is nice for most cases, but i wouldn't rely on it too much. > it makes great demos however, so i'm all in favour ;) > > at some point we should add 2 extra options: > - just check if software can be downloaded from the link (ie check url, maybe > download a few bytes?) and for the rest nothing. this could be part of some > easyconfig validator? (maybe it's there already?) > - download-only, ie download, do not build
This is what the regtest-online command line option is intended for, but it seems like it's not fully implemented (yet). But you're right, this should be a separate test, even one that could be done on the Jenkins server since it doesn't involve actual building. > if you are aware of issues with configs or blocks that prevent functional > usage, we shouldn't ship them at all. In case of MUMmer: Jens knows whether the build is functional or not. I believe it is, but only partially (only some features work). K.
