search for: ec33109

Displaying 4 results from an estimated 4 matches for "ec33109".

Did you mean: 3c93109
2018 Jan 26
1
[PATCH nbdkit] tests: Rename and rework test-ipv4.sh so it tests IPv6
I wanted to change this test so it tries connections on both IPv4 & IPv6. Having it connect on both is the easy bit. Harder was making it not fail on machines that don't have IPv6 stack (or IPv4 in some rare cases). TBH I wasn't able to test this, but it seems like this should work. In the end we want to modify nbdkit so it can listen on only certain interfaces, but that's a
2018 Jan 27
0
[PATCH nbdkit] tests: Remove QEMU_IO / HAVE_QEMU_IO.
...-io], [no]) -AM_CONDITIONAL([HAVE_QEMU_IO], [test "x$QEMU_IO" != "xno"]) - dnl See plugins/vddk/README.VDDK. AC_CHECK_SIZEOF([size_t]) AS_IF([test "x$ac_cv_sizeof_size_t" = "x4"],[bits=32],[bits=64]) diff --git a/tests/Makefile.am b/tests/Makefile.am index ec33109..9be57e6 100644 --- a/tests/Makefile.am +++ b/tests/Makefile.am @@ -178,11 +178,9 @@ file-data: # While most tests need libguestfs, testing parallel I/O is easier when # using qemu-io to kick off asynchronous requests. -if HAVE_QEMU_IO -TESTS_ENVIRONMENT += QEMU_IO=$(QEMU_IO) -TESTS += test-par...
2018 Jan 27
3
[PATCH nbdkit] tests: Remove QEMU_IO / HAVE_QEMU_IO.
Currently we test for qemu-img, socat, ss, certtool, etc at run time, but we test for qemu-io at compile time (in ./configure). This commit removes this inconsistency. I would consider the opposite patch (which makes qemu-img etc tested at configure time). The main advantage of testing for these binaries at run time is that tests are not "silently" omitted. Instead tests with
2018 Mar 08
19
[nbdkit PATCH v3 00/15] Add FUA support to nbdkit
After more than a month since v2 [1], I've finally got my FUA support series polished. This is all of my outstanding patches, even though some of them were originally posted in separate threads from the original FUA post [2], [3] [1] https://www.redhat.com/archives/libguestfs/2018-January/msg00113.html [2] https://www.redhat.com/archives/libguestfs/2018-January/msg00219.html [3]