From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/5] Fix writing events to file
Date: Mon, 20 Jun 2016 14:00:47 +0300 [thread overview]
Message-ID: <cover.1466419987.git.ed.bartosh@linux.intel.com> (raw)
Hi,
This patchset fixes "object is not JSON serializable" error caused by attempt
to convert binary pickled event object to JSON when bitbake is called with
-w command line option.
It also fixes error caused writing the same event to the file multiple times and
refactoring of event writing functionality.
The following changes since commit 09d08340fe0fca6f551c33d2fdcafb72f52812d2:
Revert "cmake.bbclass: set the modules directory correctly" (2016-06-20 08:40:21 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ed/bitbake/cooker-event-pickling-9803
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/bitbake/cooker-event-pickling-9803
Ed Bartosh (5):
cooker: move EventLogWriteHandler to the top module level
cooker: encode event objects to base64
cooker: don't remove event file
cooker: replace EventLogWriteHandler with namedtuple
cooker: clean up EvertWriter
bitbake/lib/bb/cooker.py | 114 +++++++++++++++++++++--------------------------
1 file changed, 51 insertions(+), 63 deletions(-)
--
Regards,
Ed
next reply other threads:[~2016-06-20 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 11:00 Ed Bartosh [this message]
2016-06-20 11:00 ` [PATCH 1/5] cooker: move EventLogWriteHandler to the top module level Ed Bartosh
2016-06-20 11:00 ` [PATCH 2/5] cooker: encode event objects to base64 Ed Bartosh
2016-06-20 11:00 ` [PATCH 3/5] cooker: don't remove event file Ed Bartosh
2016-06-20 11:00 ` [PATCH 4/5] cooker: replace EventLogWriteHandler with namedtuple Ed Bartosh
2016-06-20 11:00 ` [PATCH 5/5] cooker: clean up EvertWriter Ed Bartosh
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=cover.1466419987.git.ed.bartosh@linux.intel.com \
--to=ed.bartosh@linux.intel.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.