Re: [PULL 00/21] machine + QOM queue, 2020-10-05

[Igor Mammedov]

On Tue, 6 Oct 2020 17:04:18 +0200
Igor Mammedov <imammedo@redhat.com> wrote:

> On Tue, 6 Oct 2020 10:36:37 -0400
> Eduardo Habkost <ehabkost@redhat.com> wrote:
> 
> > On Tue, Oct 06, 2020 at 03:03:57PM +0100, Peter Maydell wrote:  
> > > On Mon, 5 Oct 2020 at 22:10, Eduardo Habkost <ehabkost@redhat.com> wrote: 
> > >    
> > > >
> > > > The following changes since commit 
> > > > 36d9c2883e55c863b622b99f0ebb5143f0001401:
> > > >
> > > >   readthedocs: build with Python 3.6 (2020-10-05 16:30:45 +0100)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > >   git://github.com/ehabkost/qemu.git tags/machine-next-pull-request
> > > >
> > > > for you to fetch changes up to fec5c4b6d3b7f3ffcfcbe1714e0405df6de2a222:
> > > >
> > > >   kernel-doc: Remove $decl_type='type name' hack (2020-10-05 12:48:11 
> > > > -0400)
> > > >
> > > > ----------------------------------------------------------------
> > > > machine + QOM queue, 2020-10-05
> > > >
> > > > * QOM documentation fixes and cleanups (Eduardo Habkost)
> > > > * user-mode: Prune build dependencies (Philippe Mathieu-Daudé)
> > > > * qom: Improve error message (Philippe Mathieu-Daudé)
> > > > * numa: hmat: require parent cache description before the next
> > > >   level one (Igor Mammedov)
> > > >
> > > > ----------------------------------------------------------------    
> > > 
> > > Compile failure on OSX:
> > > 
> > > ../../hw/core/numa.c:429:20: error: format specifies type 'unsigned
> > > char' but the argument has type 'int' [-Werror,-Wformat]
> > >                    node->level - 1);
> > >                    ^~~~~~~~~~~~~~~~
> > > /Users/pm215/src/qemu-for-merges/include/qapi/error.h:319:35: note:
> > > expanded from macro 'error_setg'
> > >                         (fmt), ## __VA_ARGS__)
> > >                          ~~~      ^~~~~~~~~~~
> > > 1 error generated.    
> > 
> > Is there a CI system where this is tested?  I'd like to be able
> > to detect this kind of failure before sending pull requests.  
> I usually use travis-ci, but for this patch I didn't run it via CI for some 
> reason.
> Just posted fixed v2.
> 
> (it looks like pushing to github doesn't trigger travis build anymore)
Looks like travis-ci lost previous authorizations to my github repo,
but giving a new one didn't help.

Something wrong with current QEMU master, travis-ci doesn't recognize QEMU repo 
a valid anymore.