On Tue, 10/11 22:44, P J P wrote: > +-- On Mon, 10 Oct 2016, no-re...@ec2-52-6-146-230.compute-1.amazonaws.com > wrote --+ > | Your series failed automatic build test. Please find the testing commands > and > | their output below. If you have docker installed, you can probably > reproduce it > | locally. > > I tried to build it locally(without docker), cloned submodule 'dtc' and > used > the same './configure' options as in the test. It built okay, no error. > > | === TEST SCRIPT BEGIN === > | #!/bin/bash > | set -e > | git submodule update --init dtc > | # Let docker tests dump environment info > | export SHOW_ENV=1 > | make J=8 docker-test-quick@centos6 > | make J=8 docker-test-mingw@fedora > | === TEST SCRIPT END === > | > | CC hw/timer/arm_timer.o > | CC hw/timer/arm_mptimer.o > | CC hw/timer/a9gtimer.o > > It seems to build okay. > > | (gtester:6328): GLib-WARNING **: Failed to execute test binary: > tests/test-qmp-output-visitor: Failed to fork (Resource temporarily > unavailable) > | /bin/sh: fork: retry: Resource temporarily unavailable > | make: vfork: Resource temporarily unavailable > > This seems like a system issue, not related to the 'a9gtimer.c' patch.
I think you are right, thanks for confirming! Fam
