qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Programmingkid <programmingkidx@gmail.com>
To: Cleber Rosa <crosa@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Make test
Date: Thu, 24 Aug 2017 17:50:59 -0400	[thread overview]
Message-ID: <9CE89958-B59C-4D3C-91C5-ECB4B153C43D@gmail.com> (raw)
In-Reply-To: <60e13112-931d-a517-ddb1-20c2f2de736e@redhat.com>


> On Aug 24, 2017, at 4:41 PM, Cleber Rosa <crosa@redhat.com> wrote:
> 
> 
> 
> On 08/24/2017 03:10 PM, Programmingkid wrote:
>> I think 'make test' is an abandoned testing option for QEMU so this report might be unimportant. Here is my results for running 'make test':
>> 
>> $ make test
>> make -C tests/tcg test
>>  LINK    test_path
>> Undefined symbols for architecture x86_64:
>>  "_buffer_is_zero", referenced from:
>>      _qemu_iovec_is_zero in test_path.o
>> ld: symbol(s) not found for architecture x86_64
>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>> make[1]: *** [test_path] Error 1
>> make: *** [test] Error 2
>> 
>> 
> 
> I went through the same experience, and reported it (in the form of
> patches) here:
> 
> http://lists.nongnu.org/archive/html/qemu-devel/2017-08/msg00378.html
> 
> Although it looks like you're clang, so it'd be nice to check if these
> fixes work for you too.
> 
> Regards,
> 
> -- 
> Cleber Rosa
> [ Sr Software Engineer - Virtualization Team - Red Hat ]
> [ Avocado Test Framework - avocado-framework.github.io ]
> [  7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3  ]
> 

Thank you for the patches. I will test them. I was wondering what is the point to having both 'make check' and 'make test'. It looks like everyone is using 'make check'. Maybe we are better off removing the 'make test' target.

  reply	other threads:[~2017-08-24 21:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3749.1503600836.21955.qemu-devel@nongnu.org>
2017-08-24 19:10 ` [Qemu-devel] Make test Programmingkid
2017-08-24 20:41   ` Cleber Rosa
2017-08-24 21:50     ` Programmingkid [this message]
2017-08-24 22:16       ` Cleber Rosa
2017-08-25  5:49         ` Thomas Huth
2017-08-25  9:10           ` Peter Maydell
2017-08-25  9:33             ` Fam Zheng
2017-08-25  9:41               ` Peter Maydell
2017-08-24 22:18     ` Programmingkid
2017-08-24 22:21       ` Cleber Rosa
2017-08-24 22:24         ` Programmingkid

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9CE89958-B59C-4D3C-91C5-ECB4B153C43D@gmail.com \
    --to=programmingkidx@gmail.com \
    --cc=crosa@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).