qemu-devel
[Top][All Lists]
Advanced

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

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


From: Paolo Bonzini
Subject: Re: [PULL 00/21] machine + QOM queue, 2020-10-05
Date: Tue, 6 Oct 2020 16:41:57 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0

On 06/10/20 16:36, Eduardo Habkost 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.

Possibly Cirrus CI?  You have to add it to your account
(https://cirrus-ci.org/guide/quick-start/) and then it triggers on any
push to GitHub; there's nothing else you have to do.

Paolo




reply via email to

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