From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: KVM mailing list <kvm@vger.kernel.org>
Subject: Re: Daily git testing failure due to build problem
Date: Thu, 29 Oct 2009 16:36:03 -0200 [thread overview]
Message-ID: <1256841363.3327.1.camel@localhost.localdomain> (raw)
In-Reply-To: <4AE9CBBF.1020601@siemens.com>
On Thu, 2009-10-29 at 18:07 +0100, Jan Kiszka wrote:
> Lucas Meneghel Rodrigues wrote:
> > Hi folks, today's git test failed due to a build problem. Attached goes
> > the build log. The relevant snippet I could identify is:
> >
> > 10/29 04:57:13 DEBUG| utils:0085| CC
> > [M] /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/i8259.o
> > 10/29 04:57:13 ERROR| utils:0085| /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/x86.c:80:40: error: linux/user-return-notifier.h: No such file or directory
> > 10/29 04:57:13 ERROR| utils:0085| /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/x86.c:142: error: field ‘urn’ has incomplete type
> > 10/29 04:57:13 ERROR| utils:0085| /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/x86.c: In function ‘kvm_on_user_return’:
> > 10/29 04:57:13 ERROR| utils:0085| /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/x86.c:191: warning: type defaults to ‘int’ in declaration of ‘__mptr’
> > 10/29 04:57:13 ERROR| utils:0085| /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/x86.c:191: warning: initialization from incompatible pointer type
> > 10/29 04:57:13 ERROR| utils:0085| /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/x86.c:201: error: implicit declaration of function ‘user_return_notifier_unregister’
> > 10/29 04:57:13 ERROR| utils:0085| /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/x86.c: In function ‘kvm_set_shared_msr’:
> > 10/29 04:57:13 ERROR| utils:0085| /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/x86.c:238: error: implicit declaration of function ‘user_return_notifier_register’
> > 10/29 04:57:13 ERROR| utils:0085| make[3]: *** [/usr/local/autotest/tests/kvm/src/kvm_kmod/x86/x86.o] Error 1
> > 10/29 04:57:13 ERROR| utils:0085| make[3]: *** Waiting for unfinished jobs....
> > 10/29 04:57:14 ERROR| utils:0085| make[2]: *** [/usr/local/autotest/tests/kvm/src/kvm_kmod/x86] Error 2
> > 10/29 04:57:14 DEBUG| utils:0085| make[1]: Leaving directory `/usr/src/kernels/2.6.29.6-217.2.8.fc11.x86_64'
> > 10/29 04:57:14 ERROR| utils:0085| make[1]: *** [_module_/usr/local/autotest/tests/kvm/src/kvm_kmod] Error 2
> > 10/29 04:57:14 ERROR| utils:0085| make: *** [all] Error 2
> >
> > Any doubts let me know!
>
> Find a working version in current kvm-kmod.git (at least in next, master
> should catch up soon).
The tests are made using master for kvm-kmod.git
> Are you also picking up latest kvm-kmod.git for these builds?
If necessary, I can rerun the test against the next branch to see if
this works. I will fire a job using next to see if it works.
Thanks!
> Jan
>
next prev parent reply other threads:[~2009-10-29 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 16:51 Daily git testing failure due to build problem Lucas Meneghel Rodrigues
2009-10-29 17:07 ` Jan Kiszka
2009-10-29 18:36 ` Lucas Meneghel Rodrigues [this message]
2009-10-29 19:01 ` Lucas Meneghel Rodrigues
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=1256841363.3327.1.camel@localhost.localdomain \
--to=lmr@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.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