From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Marc-André Lureau" <mlureau@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 000/180] QAPI patches for 2017-01-16
Date: Mon, 23 Jan 2017 12:48:14 +0000 [thread overview]
Message-ID: <871svuaqnl.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA8ckibWjvDQGyBTGSGmrZQGUbojQmuHqnm=EPg=Vh7L1g@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On 20 January 2017 at 15:46, Markus Armbruster <armbru@redhat.com> wrote:
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>
>>> On 17 January 2017 at 16:43, Peter Maydell <peter.maydell@linaro.org> wrote:
>>>> In any case, applied this pullreq to master.
>>>
>>> Although it works fine on my OSX box (with warnings) it seems
>>> to have broken the Travis OSX builds:
>>> https://travis-ci.org/qemu/qemu/jobs/192750574
>>>
>>> GEN qemu-options.texi
>>> GEN qemu-monitor.texi
>>> GEN qemu-img-cmds.texi
>>> GEN qemu-monitor-info.texi
>>> GEN qemu-doc.txt
>>> qemu-doc.texi:7: warning: unrecognized encoding name `UTF-8'.
>>> GEN qemu-img.1
>>> /Users/travis/build/qemu/qemu//qemu-options.texi:60: warning: unlikely
>>> character [ in @var.
>>> /Users/travis/build/qemu/qemu//qemu-options.texi:60: warning: unlikely
>>> character ] in @var.
>>> /Users/travis/build/qemu/qemu//qemu-options.texi:61: warning: unlikely
>>> character [ in @var.
>>> /Users/travis/build/qemu/qemu//qemu-options.texi:61: warning: unlikely
>>> character ] in @var.
>>> /Users/travis/build/qemu/qemu//qemu-options.texi:630: No matching `@end table'.
>>> /Users/travis/build/qemu/qemu//qemu-doc.texi:1419: Cross reference to
>>> nonexistent node `bt-hcis' (perhaps incorrect sectioning?).
>>> makeinfo: Removing output file `qemu-doc.txt' due to errors; use
>>> --force to preserve.
>>> make: *** [qemu-doc.txt] Error 1
>>
>> @table and @end table are nested correctly in my generated
>> qemu-options.texi, and @anchor{bt-hcis} is present. Can you grab the
>> offending qemu-options.texi for me?
>
> Alex may know how to get objects out of a failed Travis build
> (if it's possible at all).
For the normal targets we can re-create builds at our leisure using the
travis docker image. Unfortunately I'm not clear on how this works for
the MacOSX build.
The best solution I can come up with is to tweak your build to dump the
.text into stdout and then look on the Travis web-page as the build
fails. I had a similar fall-back encoded when debugging the clang build,
something like:
before_script:
- ./configure ${CONFIG} --extra-cflags="-g3 -O0 -fsanitize=thread -fuse-ld=gold" || cat config.log
So change your local .travis.yml to:
- env: CONFIG=""
os: osx
compiler: clang
script: make -j3 || cat qemu-options.texi
and trigger a build with it.
--
Alex Bennée
next prev parent reply other threads:[~2017-01-23 12:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 9:33 [Qemu-devel] [PULL v2 000/180] QAPI patches for 2017-01-16 Markus Armbruster
2017-01-16 15:58 ` Peter Maydell
2017-01-17 8:31 ` Markus Armbruster
2017-01-17 9:54 ` Marc-André Lureau
2017-01-17 10:13 ` Markus Armbruster
2017-01-17 11:08 ` Peter Maydell
2017-01-17 12:08 ` Markus Armbruster
2017-01-17 12:24 ` Peter Maydell
2017-01-17 13:24 ` Markus Armbruster
2017-01-17 13:59 ` Peter Maydell
2017-01-17 14:15 ` Marc-André Lureau
2017-01-17 14:23 ` Markus Armbruster
2017-01-17 16:43 ` Peter Maydell
2017-01-20 14:39 ` Peter Maydell
2017-01-20 15:46 ` Markus Armbruster
2017-01-20 15:48 ` Peter Maydell
2017-01-23 12:48 ` Alex Bennée [this message]
2017-01-23 13:59 ` Daniel P. Berrange
2017-01-23 14:49 ` Markus Armbruster
2017-01-24 9:53 ` Markus Armbruster
2017-01-24 10:03 ` Peter Maydell
2017-01-24 11:08 ` Markus Armbruster
2017-01-24 10:09 ` Markus Armbruster
2017-01-24 10:49 ` Paolo Bonzini
2017-01-17 17:05 ` Eric Blake
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=871svuaqnl.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=mlureau@redhat.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.