public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] oeqa.buildperf: be sure to use the latest buildstats
Date: Wed,  7 Sep 2016 10:28:46 +0300	[thread overview]
Message-ID: <1473233326-16830-3-git-send-email-markus.lehtonen@linux.intel.com> (raw)
In-Reply-To: <1473233326-16830-1-git-send-email-markus.lehtonen@linux.intel.com>

Be sure to take the latest buildstats if multiple buildstats are found.

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
---
 meta/lib/oeqa/buildperf/base.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/buildperf/base.py b/meta/lib/oeqa/buildperf/base.py
index 7dfb2bf..9700c05 100644
--- a/meta/lib/oeqa/buildperf/base.py
+++ b/meta/lib/oeqa/buildperf/base.py
@@ -466,7 +466,7 @@ class BuildPerfTestCase(unittest.TestCase):
             return bs_json
 
         log.info('Saving buildstats in JSON format')
-        bs_dirs = os.listdir(self.bb_vars['BUILDSTATS_BASE'])
+        bs_dirs = sorted(os.listdir(self.bb_vars['BUILDSTATS_BASE']))
         if len(bs_dirs) > 1:
             log.warning("Multiple buildstats found for test %s, only "
                         "archiving the last one", self.name)
-- 
2.6.6



      parent reply	other threads:[~2016-09-07  7:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07  7:28 [PATCH 0/2] Fixes for oe-build-perf-test Markus Lehtonen
2016-09-07  7:28 ` [PATCH 1/2] oeqa.buildperf: try harder when splitting 'nevr' string Markus Lehtonen
2016-09-07  7:28 ` Markus Lehtonen [this message]

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=1473233326-16830-3-git-send-email-markus.lehtonen@linux.intel.com \
    --to=markus.lehtonen@linux.intel.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox