search for: harness

...n't accidentally regress some old OS/hypervisor combination while making changes. The test cases are going to be huge, so we cannot possibly distribute them in libguestfs. Furthermore many of them have licensing problems which means we cannot redistribute them at all. This commit adds a test harness which can be used by two external test suites - a free one containing the redistributable test cases, and a proprietary one. Both will link to the same test harness provided by this commit. For more information, see the 'virt-v2v-test-harness(1)' man page. Rich.

See the new man page virt-v2v-test-harness(1) added in this commit for details of this library/harness, and also how to get the external tests. --- .gitignore | 6 + Makefile.am | 3 + README | 2 + configure.ac...

...rts basic object-file level mocking and testing. That last one is unusual so I want to expand on it. The llvm-jitlink tool acquired a couple of new options to support this feature: "--phony-externals" which resolves all otherwise unresolved symbols to null instead of erroring, and "-harness" which allows a set of objects to be designated as a test harness, with the regular object files implicitly treated as objects to be tested. If the -harness option is passed llvm-jitlink installs a JITLink plugin to make some modifications to the usual linker rules: -- All symbols referenced...

v7: The only changes since v6 are those suggested by Pino in the review of v5.

I should probably start by saying this patch series isn't ready for review yet. This patch series adds a test harness to libguestfs. It allows us to run the tests outside the ordinary 'make check' path in the build tree. In particular, you can use this to run tests when libguestfs has been installed. 'make check' and the other 'make check-*' rules still work. The goals for this series i...

This is a more complete patch to add the test harness. The only parts missing now are the language bindings (except OCaml). The language bindings need a bit more thought. At the moment most language binding tests are done through some sort of shell script like perl/run-perl-tests which either runs each test itself or uses some language-specific mach...

Since v2: - Add perl tests. - Reworked and fixed the tests for virt-builder. - Some further minor bug fixes.

Hi, I used the commands below to make Hartley's table, but some values are NA. require(SuppDists) trat = seq(2, 15, 1) gl = seq(2, 40, 1) har = matrix(0, nr=length(gl), nc=length(trat)) for(i in 1:length(gl)) for(j in 1:length(trat)) har[i,j] <- qmaxFratio(.95, df=gl[i], k=trat[j]) rownames(har) <- gl colnames(har) <- trat head(har) The output (head): 2

Dear community, LLVM test-suite includes both default applications (benchmarks, tests) and test harness (CMake modules, lit-support, some scripts, etc.). Test suite provides extension interface to add "external" tests suite and folders. This worked well, we enhanced basic harness and integrated large set of internal benchmarks and applications. However, we have users interested in LLVM tes...

This converts more of the tests (basically everything under tests/) to use the test harness, revealing some problems which have subsequently been fixed. Rich.

Dear R users I have built several glmm models using glmmPQL in the following structure: m1<-glmmPQL(dev~env*har*treat+dens, random = ~1|pop/rep, family = Gamma) (full script below, data attached) I have tried all the methods I can find to obtain some sort of model fit score or to compare between models using following the deletion of terms (i.e. AIC, logLik, anova.lme(m1,m2)), but I

For v6: This is mainly just a rebase, but I have also added tests in the ocaml/ language bindings directory, and for all the OCaml-written virt tools. Rich.

Since v3: - A large number of fixes, especially for running the tests on installed libguestfs. - Fixed EXTRA_DIST rules throughout. - Extra patch 17/17 which is a tidy-up of the generated XML listing guests. Rich.

Since v4: - More tests have been converted. - Testing local guests fixed. - Drop no-exec-stack test.

Help R list servers, I have 500 external data sets for a simulation study that I would like to bring into R to analyze. They have the names data1.dat, data2.dat, ..., dataN.dat Is there a way to automatize the bringing in of these data sets in R using the read.table function within a looping cycle? For example... for (j in 1:N){ data_"j" = read.table("data"j".dat,

...xt > > Michael > > > > > 2018-07-09 2:26 GMT-05:00 Elena Lepilkina via llvm-dev > <llvm-dev at lists.llvm.org>: >> Dear community, >> >> >> >> LLVM test-suite includes both default applications (benchmarks, tests) and >> test harness (CMake modules, lit-support, some scripts, etc.). Test suite >> provides extension interface to add “external” tests suite and folders. This >> worked well, we enhanced basic harness and integrated large set of internal >> benchmarks and applications. >> >> >>...

We would like to have a more flexible way to run tests, including running them on an installed copy of libguestfs, running them in parallel, and being able to express dependencies and ordering between tests and data files properly. Therefore introduce a test harness (test-harness) program which can run tests either from the locally built copy, or from an installed copy of the tests (in $libdir/guestfs/tests). The test harness is backwards compatible on the command line, ie. 'make check', 'make -C inspector check-valgrind' etc. will still work....

This has got to the stage where it actually works, both for running the tests in-tree and installed. The 'test-harness' script has become rather over-complex in the process however. Rich.

Hey I am just organizing the CentOS village at HAR and need a rough estimate of people who will be attending. What do people want? Shall the CentOS people have their own party tent? We are currently with the Fedora people. I will also post on the SL mailing list. Hope to see you all at HAR? Cheers Didi ---- My www page: www.ribalba.de Email / Jabber: ribalba at gmail.com Skype : ribalba

On Tue, Oct 21, 2014 at 05:56:14PM +0200, Pino Toscano wrote: > On Sunday 05 October 2014 14:08:35 Richard W.M. Jones wrote: > > +# Install the test harness. > > +localtestsdir = $(alltestsdir) > > +localtests_SCRIPTS = ../test-harness > > Shouldn't it rather go to libexec? No, it's meant to be run by the end user. > > +../test-harness: > > + rm -f $@ $@-t > > + echo 'echo Warning: Install...