search for: script4

...nit, just like virt-sparsify already does. Expand the test-virt-sysprep-script.sh test to ensure that virt-sysprep is not affected again by this issue. --- .gitignore | 1 + builder/builder.ml | 2 ++ sysprep/main.ml | 2 ++ sysprep/script4.sh | 21 +++++++++++++++++++++ sysprep/test-virt-sysprep-script.sh | 22 +++++++++++++++++++++- 5 files changed, 47 insertions(+), 1 deletion(-) create mode 100755 sysprep/script4.sh diff --git a/.gitignore b/.gitignore index 74661b0..d9bef99 100644 --- a/.gitignore +++ b/.gitign...

...a/sysprep/test-virt-sysprep-script.sh b/sysprep/test-virt-sysprep-script.sh index 409a9b7..49d0756 100755 --- a/sysprep/test-virt-sysprep-script.sh +++ b/sysprep/test-virt-sysprep-script.sh @@ -32,7 +32,7 @@ fi # Check that multiple scripts can run. rm -f stamp-script1.sh stamp-script2.sh stamp-script4.sh -if ! virt-sysprep -q -n -a ../test-data/phony-guests/fedora.img --enable script \ +if ! virt-sysprep -q -n --format raw -a ../test-data/phony-guests/fedora.img --enable script \ --script $abs_srcdir/script1.sh --script $abs_srcdir/script2.sh; then echo "$0: virt-sysprep wasn&...

Hi, small series with small improvements to the tests. Pino Toscano (3): tests: specify the image format when possible tests: remove remaining relative paths to binaries fish: generate test-prep.sh with generator .gitignore | 1 + align/test-virt-alignment-scan.sh | 2 +- cat/Makefile.am | 2 +- cat/test-virt-cat.sh

...fy/.depend -/sparsify/link.sh /sparsify/stamp-virt-sparsify.pod /sparsify/virt-sparsify /sparsify/virt-sparsify.1 @@ -476,7 +471,6 @@ Makefile.in /stamp-guestfs-release-notes.pod /stamp-h1 /sysprep/.depend -/sysprep/link.sh /sysprep/stamp-script1.sh /sysprep/stamp-script2.sh /sysprep/stamp-script4.sh @@ -566,7 +560,6 @@ Makefile.in /v2v/centos-6.img /v2v/centos-7.0.img /v2v/fedora-20.img -/v2v/link.sh /v2v/oUnit-* /v2v/rhel-5.10.img /v2v/rhel-6.5.img diff --git a/builder/Makefile.am b/builder/Makefile.am index bfe2f79..182f5a4 100644 --- a/builder/Makefile.am +++ b/builder/Makefile.am...

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 machinary to run each test. The problem with that

These are my thoughts on adding a test harness to run tests instead of using automake. The aim of this exercise is to allow us to run the full test suite on an installed copy of libguestfs. Another aim is to allow us to work around all the limitations and problems of automake. The first patch makes an observation that since the ./run script sets up $PATH to contain all the directories

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

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.

Previously I posted a work-in-progress preview of this patch series: https://www.redhat.com/archives/libguestfs/2017-February/msg00224.html This is the finished version that updates all of the shell-script based tests. It passes 'make check', 'make check-direct' and 'make check-slow'. Rich.

...plete the operation. This is just an estimate. diff --git a/sysprep/Makefile.am b/sysprep/Makefile.am index 66e2ceb..a000735 100644 --- a/sysprep/Makefile.am +++ b/sysprep/Makefile.am @@ -21,6 +21,7 @@ EXTRA_DIST = \ $(SOURCES_MLI) $(SOURCES_ML) $(SOURCES_C) \ script1.sh script2.sh script3.sh script4.sh \ test-virt-sysprep.sh \ + test-virt-sysprep-docs.sh \ test-virt-sysprep-passwords.sh \ test-virt-sysprep-script.sh \ virt-sysprep.pod @@ -178,8 +179,11 @@ TESTS_ENVIRONMENT = \ PATH=$(abs_top_builddir)/fuse:$(PATH) \ $(top_builddir)/run --test -if ENABLE_APPLIANCE TESTS = \ + tes...

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...