All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH] runningbuild.py: fix goggle ui
Date: Mon, 19 Mar 2012 12:56:19 +0100	[thread overview]
Message-ID: <1332158179-2776-1-git-send-email-eric@eukrea.com> (raw)

* goggle ui actually fails with :
Traceback (most recent call last):
  File ".../bitbake/lib/bb/ui/goggle.py", line 35, in event_handle_idle_func
    build.handle_event (event, pbar)
  File ".../bitbake/lib/bb/ui/crumbs/runningbuild.py", line 234, in handle_event
    pbar.update(0, None, bb.event.getName(event))
TypeError: update() takes exactly 3 arguments (4 given)

Signed-off-by: Eric Bénard <eric@eukrea.com>
---
 lib/bb/ui/crumbs/runningbuild.py |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/bb/ui/crumbs/runningbuild.py b/lib/bb/ui/crumbs/runningbuild.py
index 718f692..10ca394 100644
--- a/lib/bb/ui/crumbs/runningbuild.py
+++ b/lib/bb/ui/crumbs/runningbuild.py
@@ -231,8 +231,8 @@ class RunningBuild (gobject.GObject):
                                       HobColors.OK,
                                       0))
             if pbar:
-                pbar.update(0, None, bb.event.getName(event))
-                pbar.set_title()
+                pbar.update(0, self.progress_total)
+                pbar.set_title(bb.event.getName(event))
 
         elif isinstance(event, bb.event.BuildCompleted):
             failures = int (event._failures)
-- 
1.7.7.6




             reply	other threads:[~2012-03-19 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 11:56 Eric Bénard [this message]
2012-03-20 14:13 ` [PATCH] runningbuild.py: fix goggle ui Richard Purdie
  -- strict thread matches above, loose matches on Subject: below --
2012-03-21 15:44 Eric Bénard
2012-03-22  1:10 ` Joshua Lock

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=1332158179-2776-1-git-send-email-eric@eukrea.com \
    --to=eric@eukrea.com \
    --cc=bitbake-devel@lists.openembedded.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.