search for: target_stat

Displaying 16 results from an estimated 16 matches for "target_stat".

2015 Jan 14
2
[LLVMdev] 3.5.1 Testing Phase II Begins
...the record: http://reviews.llvm.org/D6812 fixes most of these big- > endian N32 failures but we should stick to the current plan because I haven't > retested the other ABI's yet. > All but one of the remaining failures is due a qemu bug. The linux user mode > emulation of struct target_stat doesn't quite match any supported by glibc and > causes certain stat() calls to return -1. > This is fixed in my working copy of qemu and I'll upstream it soon. The last > failure is that lemon's output is wrong. I don't know the cause yet. The lemon failure turned out to...
2014 Dec 29
2
[LLVMdev] 3.5.1 Testing Phase II Begins
On Tue, Dec 23, 2014 at 09:27:32PM +0000, Daniel Sanders wrote: > clang+llvm-3.5.1-rc2-mips-linux-gnu.tar.xz: > All ok for default options and -mips32. > > clang+llvm-3.5.1-rc2-mipsel-linux-gnu.tar.xz: > All ok for default options. > It will take a couple days to get results for the -mips32 test-suite (there's no FPU or local disk on this machine so some tests
2014 Oct 03
0
[PATCH v3] tests: Introduce test harness for running tests.
...h "make-guests-all-good.pl failed"; + + let cmd = "rm -f *.tmp.*" in + ignore (Sys.command cmd); + ) + + (* Like 'make', run a rule if target does not exist, or if target is + * older than any of the sources. + *) + and rule target sources f = + let target_stat = + try Some (stat target) + with Unix_error (ENOENT, _, _) -> + (* Target file does not exist. *) + printf "test-harness: building %s\n%!" target; + f (); None in + match target_stat with + | None -> () + | Some target_stat -> + let r...
2018 Jul 20
4
Relinking (syscall-free) ELF executable into Mach-O and PE executables
Hi, Let's suppose we have an ELF executable that doesn't issue any syscall (I mean, syscalls are issued from an external dynamic library, not from the executable, and we can ignore such dynamic library because we have the proper equivalent library with the proper syscalls in MacOS and Windows). So, the question: Is it "currently possible" (by "currently possible" I
2014 Oct 05
0
[PATCH v5 1/7] tests: Introduce test harness for running tests.
...h "make-guests-all-good.pl failed"; + + let cmd = "rm -f *.tmp.*" in + ignore (Sys.command cmd); + ) + + (* Like 'make', run a rule if target does not exist, or if target is + * older than any of the sources. + *) + and rule target sources f = + let target_stat = + try Some (stat target) + with Unix_error (ENOENT, _, _) -> + (* Target file does not exist. *) + printf "test-harness: building %s\n%!" target; + f (); None in + match target_stat with + | None -> () + | Some target_stat -> + let r...
2015 Aug 06
0
[PATCH v4 01/17] tests: Introduce test harness for running tests.
...h "make-guests-all-good.pl failed"; + + let cmd = "rm -f *.tmp.*" in + ignore (Sys.command cmd); + ) + + (* Like 'make', run a rule if target does not exist, or if target is + * older than any of the sources. + *) + and rule target sources f = + let target_stat = + try Some (stat target) + with Unix_error (ENOENT, _, _) -> + (* Target file does not exist. *) + printf "test-harness: building %s\n%!" target; + f (); None in + match target_stat with + | None -> () + | Some target_stat -> + let r...
2014 Oct 04
4
[PATCH v4 0/4] tests: Introduce test harness for running tests.
This converts more of the tests (basically everything under tests/) to use the test harness, revealing some problems which have subsequently been fixed. Rich.
2014 Oct 05
12
[PATCH v5 0/7] tests: Introduce test harness for running tests.
Since v4: - More tests have been converted. - Testing local guests fixed. - Drop no-exec-stack test.
2014 Oct 23
10
[PATCH v6 00/10] tests: Introduce test harness for running tests.
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.
2014 Oct 24
10
[PATCH v7 00/10] tests: Introduce test harness for running tests.
v7: The only changes since v6 are those suggested by Pino in the review of v5.
2015 Jul 28
10
[PATCH 00/10] tests: Introduce test harness for running tests.
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
2015 Aug 06
20
[PATCH v4 00/17] tests: Introduce test harness for running tests.
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.
2015 Jul 31
14
[PATCH v2 00/14] tests: Introduce test harness for running tests.
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
2015 Aug 04
16
[PATCH v3 01/16] tests: Introduce test harness for running tests.
Since v2: - Add perl tests. - Reworked and fixed the tests for virt-builder. - Some further minor bug fixes.
2020 May 29
15
[RFC 00/12] Audio DSP VirtIO and vhost drivers
This patch set is a follow up to "Add a vhost RPMsg API" [1], it is marked as an RFC because firstly it depends on the RPMsg API series and secondly it is currently being reviewed on ALSA and SOF mailing lists, but any early comments from virtualisation developers would be highly appreciated too! Thanks Guennadi [1]
2020 May 29
15
[RFC 00/12] Audio DSP VirtIO and vhost drivers
This patch set is a follow up to "Add a vhost RPMsg API" [1], it is marked as an RFC because firstly it depends on the RPMsg API series and secondly it is currently being reviewed on ALSA and SOF mailing lists, but any early comments from virtualisation developers would be highly appreciated too! Thanks Guennadi [1]