On Tue, 1 Dec 2015, Willem Jan Withagen wrote: > On 1-12-2015 14:30, Sage Weil wrote: > > On Tue, 1 Dec 2015, Willem Jan Withagen wrote: > > > On 30-11-2015 14:21, Sage Weil wrote: > > > > The problem with all of the porting code in general is that it is doomed > > > > to break later on if we don't have (at least) ongoing build tests. In > > > > order for a FreeBSD or OSX port to continue working we need VMs that run > > > > either gitbuilder or a jenkins job or similar so that we can tell when > > > > it > > > > breaks. > > > > > > > > If someone is willing to run a VM somewhere to do this we can pretty > > > > easily stick it on the gitbuilder page at > > > > > > > > http://ceph.com/gitbuilder.cgi > > > > > > > > > Hi Sage, > > > > > > Could you give some pointers as to where to start running the tests. > > > I see a lot of "basic" tests to see if the platform is actually > > > conformant. > > > > > > So before plunging into running ceph-mon and stuff, it would perhaps be > > > better to actually run (parts of) the basic required tests.. > > > > I would start with 'make check' from src/... that's what we'd actually > > want the gitbuilder to do. > > I was running that at the moment.... > Found the suggestion on the developers pages, in the manual section. > Sort of hidden at the bottom. :) > > Did kill it in between, but now when I run it, it just only generates the > report. > So I just went make clean, which is rather too much... > But could not really figure out the makefiles in test (yet) > > How do I reset the test results? I don't think there is anything to reset... just re-ru make check. The exception is probably just if you hit control-c but it left running processes behind (./stop.sh should clean those up). At least, that's the case on Linux.. maybe the (auto)tools are a bit different on *BSD? sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
