On Mon, Dec 1, 2014 at 12:15 PM, Antti Kantee <po...@netbsd.org> wrote: >> Antti, Justin, can we separate the rump userland from the rump kernel >> binaries easily and put them in different sets, and then run the userland >> from -6 or -7 against the (rump-)kernel from -current? > > > Copying prebuilt userland tarballs around sounds suboptimal. Unless you > want to go cherry-picking every time something changes in the tests, you'd > need all of bins/libs. And then you'd probably need to carefully tune your > PATH for the tests to still work. Instead, I'd go the opposite route which > allows for straightforward, self-contained automation: > > You can use buildrump.sh (*) with a -6 or -7 toolchain to get a -current > rump kernel. Theoretically speaking, you can then run the -current tests as > an additional part of -6 and -7 test runs with LD_LIBRARY_PATH set to > buildrump.sh/rump/lib. I doubt anyone has run /usr/tests with host != rump > kernel since I was working on NetBSD 5.0 and testing -current, um, 4 years > ago (and I was just installing -current to /), so expect some tuning to be > necessary.
Well I have now, the buildrump snapshot (ie current a month or so ago) on 6.1.5/amd64. There are about 110 more test fails than there are on my install, will look into what type of thing is failing and why. A lot (most) seem to be puffs/p2k related. Justni