qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL v3 00/35] Misc patches for 2018-12-18


From: Peter Maydell
Subject: Re: [Qemu-devel] [PULL v3 00/35] Misc patches for 2018-12-18
Date: Thu, 20 Dec 2018 17:41:32 +0000

On Thu, 20 Dec 2018 at 17:38, Peter Maydell <address@hidden> wrote:
>
> On Thu, 20 Dec 2018 at 12:37, Paolo Bonzini <address@hidden> wrote:
> >
> > The following changes since commit e85c577158a2e8e252414959da9ef15c12eec63d:
> >
> >   Merge remote-tracking branch 
> > 'remotes/huth-gitlab/tags/pull-request-2018-12-17' into staging (2018-12-18 
> > 14:31:06 +0000)
> >
> > are available in the Git repository at:
> >
> >   git://github.com/bonzini/qemu.git tags/for-upstream
> >
> > for you to fetch changes up to b4e8bbb9ae50045160957e7ab66c4f1cae535ea4:
> >
> >   avoid TABs in files that only contain a few (2018-12-19 16:03:22 +0100)
> >
> > ----------------------------------------------------------------
> > * HAX support for Linux hosts (Alejandro)
> > * esp bugfixes (Guenter)
> > * Windows build cleanup (Marc-André)
> > * checkpatch logic improvements (Paolo)
> > * coalesced range bugfix (Paolo)
> > * switch testsuite to TAP (Paolo)
> > * QTAILQ rewrite (Paolo)
> > * block/iscsi.c cancellation fixes (Stefan)
> > * improve selection of the default accelerator (Thomas)
>
> This seemed to work on most of my test hosts but something
> weird happened here: hyperlong repetitive command line and
> looks like make got an "fwrite(): Resource temporarily unavailable"
> halfway through writing it out??
>
> This was on my x86-64 Linux Ubuntu system, clang build
> which I configure with '--cc=clang' '--cxx=clang++' '--enable-gtk'
> '--extra-cflags=-fsanitize=undefined  -fno-sanitize=shift-base -Werror';
> the error is during the 'make -C build/clang check V=1' phase.

Checking my logfiles I think that the previous pull request
apply attempt also failed this way, but I didn't notice
because of the other failures on other hosts. It may be
the combination of the huge command line and the way my
test setup uses GNU parallel and ssh to capture the make
output into a logfile.

thanks
-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]