All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.g.lock@intel.com>
To: yocto@yoctoproject.org
Subject: [yocto autobuilder][PATCH 0/3] Fix buildlogger
Date: Wed,  7 Sep 2016 16:33:38 +0100	[thread overview]
Message-ID: <cover.1473261757.git.joshua.g.lock@intel.com> (raw)

Since build 999 we haven't seen any builds logged to the BuildLogs wiki page,
that turns out to be because the JSON dicts keys are strings and thus the sort
order isn't as expected, i.e. 999 > 1001.

This series tidies up the buildlogger some and includes a fix for this issue by
converting the keys of the dicts to a list of ints and sorting that to determine
the most recent build.

The following changes since commit ba01fe19440a91091fe15544ecc2809a79f19401:

  nightly-qa-systemd.conf: Add create_eventlog property (2016-08-31 21:22:11 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/yocto-autobuilder joshuagl/buildlogger
  http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/log/?h=joshuagl/buildlogger

Joshua Lock (3):
  buildlogger: remove old, incomplete, comment
  buildlogger: don't hardcode YP AB in generated URL
  buildlogger: fix sorting of recent builds

 bin/buildlogger              | 23 +++++++++++++----------
 etc/buildlogger.conf.example |  1 +
 2 files changed, 14 insertions(+), 10 deletions(-)

-- 
2.7.4


             reply	other threads:[~2016-09-07 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 15:33 Joshua Lock [this message]
2016-09-07 15:33 ` [yocto autobuilder][PATCH 1/3] buildlogger: remove old, incomplete, comment Joshua Lock
2016-09-07 15:33 ` [yocto autobuilder][PATCH 2/3] buildlogger: don't hardcode YP AB in generated URL Joshua Lock
2016-09-07 15:33 ` [yocto autobuilder][PATCH 3/3] buildlogger: fix sorting of recent builds Joshua Lock
2016-09-08 12:07 ` [yocto autobuilder][PATCH 0/3] Fix buildlogger Beth 'pidge' Flanagan

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.1473261757.git.joshua.g.lock@intel.com \
    --to=joshua.g.lock@intel.com \
    --cc=yocto@yoctoproject.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.