All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Stefan Weil <sw@weilnetz.de>,
	Daniel Gollub <gollub@b1-systems.de>,
	qemu-devel@nongnu.org, Stefan Weil <weil@mail.berlios.de>
Subject: Re: [Qemu-devel] buildbot failure in qemu on block_mingw32
Date: Thu, 10 Jan 2013 14:08:47 +0100	[thread overview]
Message-ID: <50EEBD5F.2000007@redhat.com> (raw)
In-Reply-To: <20130110124422.GF30946@stefanha-thinkpad.redhat.com>

  Hi,

>> I don't get this error in line 2097 with my native and cross builds,
>> nor do I get the warnings. Which version of MinGW is used on the buildbot?
>>
>> Anyway, it will be fixed with the pending patch
>> http://patchwork.ozlabs.org/patch/210240/
> 
> I've added Gerd on CC if he has time to check the buildbot.  But since
> this will be fixed anyway it probably doesn't matter.

http://buildbot.b1-systems.de/qemu/buildslaves/kraxel_rhel61
has package version lists.

And, yes, mingw64 builds it fine, both 32 and 64 bit versions.

While talking about the buildbots (adding Daniel to Cc):

kraxel_fedora16 has mingw64 installed and can so both 32bit and 64bit
mingw builds.  The cross prefixes are "i686-w64-mingw32-" and
"x86_64-w64-mingw32-".

Both kraxel_fedora16 and kraxel_rhel61 have clang installed, which can
be configured like this:

clang.addStep(Configure(command=["./configure",
                                 "--cc=clang",
                                 "--host-cc=clang",
                                 "--disable-werror",
                                 "--disable-debug-info"],
                        logfiles={"config.log": "config.log"}))

Finally, a custom message formater which adds the log tail directly to
the fail messages would be cool, so you don't have to dig out the web
browser to figure what the error is.  /me runs this one:

def kraxelMessageFormatter(mode, name, build, results, master_status):
    result = Results[results]
    defmsg = mail.defaultMessage(mode, name, build, results, master_status);
    text = list();
    text.append(defmsg['body']);

    # get log for last step
    logs = build.getLogs()
    for log in reversed(logs):
        if log.getName() == 'stdio':
            break
    content = log.getText().splitlines() # Note: can be VERY LARGE
    url = "%s/steps/%s/logs/%s" % (master_status.getURLForThing(build),
                                   log.getStep().getName(),
                                   log.getName())

    # append log info to standard message
    text.append("========== log tail ==========")
    for line in content[-32:]:
        text.append(unicode(line,'utf8'))
    text.append("")
    text.append("========== full log ==========")
    text.append(url);

    return { 'body' : "\n".join(text), 'type' : 'plain' }

... hook up this way ...

mn = mail.MailNotifier($args,
                       messageFormatter=kraxelMessageFormatter);

cheers,
  Gerd

  reply	other threads:[~2013-01-10 13:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08  0:06 [Qemu-devel] buildbot failure in qemu on block_mingw32 qemu
2013-01-09  8:53 ` Stefan Hajnoczi
2013-01-09 17:16   ` Stefan Weil
2013-01-10 12:44     ` Stefan Hajnoczi
2013-01-10 13:08       ` Gerd Hoffmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-16  0:06 qemu
2012-12-17  0:23 qemu
2012-11-20  0:04 qemu
2012-11-20 13:36 ` Stefan Hajnoczi
2012-11-20 13:49   ` Anthony Liguori
2012-10-24  1:05 qemu
2012-10-24  9:16 ` Kevin Wolf
2012-10-24 11:39   ` Luiz Capitulino
2012-10-20  1:04 qemu
2012-10-22 12:30 ` Kevin Wolf
2012-10-22 13:54   ` Corey Bryant
2012-09-20  6:12 qemu
2012-09-15  1:06 qemu
2012-09-08  1:38 qemu
2012-08-15  1:04 qemu
2012-08-09  1:04 qemu
2012-08-07  1:03 qemu
2012-07-11  1:04 qemu
2012-06-08  1:54 qemu
2012-06-08  9:07 ` Stefan Hajnoczi
2012-06-08  9:51   ` Max Filippov
2012-06-05  1:50 qemu
2012-05-10  1:04 qemu
2012-05-10  7:28 ` Paolo Bonzini
2012-04-04  1:43 qemu
2012-03-03  2:05 qemu
2012-03-03  9:06 ` Stefan Weil
2012-02-20  6:44 qemu
2012-01-24  2:05 qemu
2011-12-16  2:06 qemu
2011-11-23  2:04 qemu

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=50EEBD5F.2000007@redhat.com \
    --to=kraxel@redhat.com \
    --cc=gollub@b1-systems.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=sw@weilnetz.de \
    --cc=weil@mail.berlios.de \
    /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.