All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 00/10] Revive ptest and add result to buildhistory
Date: Mon, 31 Jul 2017 02:50:00 -0700	[thread overview]
Message-ID: <cover.1501494496.git.liezhi.yang@windriver.com> (raw)

We can get the regression result by:
$ git show HEAD ptest_log/pass.fail.skip.*

Can we add ptest to default TEST_SUITES, please ?

// Robert

The following changes since commit a2ab288bd002ebb6e64d46e941fb122e1157ff49:

  uninative: Update to 1.7 uninative release (2017-07-30 08:45:49 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/ptest
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/ptest

Robert Yang (10):
  oeqa/targetcontrol.py: simplify checking for qemu_use_kvm
  runtime/cases/_ptest.py: revive it
  oeqa/utils/logparser.py: add skip status
  runtime/cases/_ptest.py: add skip status
  runtime/cases/_ptest.py: rename it to ptest.py
  utils/logparser.py: fix section check
  core/target/ssh.py: replace decode errors
  buildhistory.bbclass: print message when no commit
  buildhistory.bbclass: add ptest_log
  testimage.bbclass: update comments

 meta/classes/buildhistory.bbclass     |  30 ++++++++++
 meta/classes/testimage.bbclass        |   4 +-
 meta/lib/oeqa/core/target/ssh.py      |   4 +-
 meta/lib/oeqa/runtime/cases/_ptest.py | 103 ----------------------------------
 meta/lib/oeqa/runtime/cases/ptest.py  |  82 +++++++++++++++++++++++++++
 meta/lib/oeqa/targetcontrol.py        |   5 +-
 meta/lib/oeqa/utils/logparser.py      |   7 ++-
 7 files changed, 122 insertions(+), 113 deletions(-)
 delete mode 100644 meta/lib/oeqa/runtime/cases/_ptest.py
 create mode 100644 meta/lib/oeqa/runtime/cases/ptest.py

-- 
2.11.0



             reply	other threads:[~2017-07-31  9:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31  9:50 Robert Yang [this message]
2017-07-31  9:50 ` [PATCH 01/10] oeqa/targetcontrol.py: simplify checking for qemu_use_kvm Robert Yang
2017-08-08 15:30   ` Richard Purdie
2017-08-09  9:46     ` Robert Yang
2017-08-21  8:02       ` Robert Yang
2017-08-21 20:35         ` Richard Purdie
2017-08-22  1:08           ` Robert Yang
2017-08-09  9:46     ` Robert Yang
2017-07-31  9:50 ` [PATCH 02/10] runtime/cases/_ptest.py: revive it Robert Yang
2017-07-31 13:38   ` Paul Eggleton
2017-08-01  2:03     ` Robert Yang
2017-07-31  9:50 ` [PATCH 03/10] oeqa/utils/logparser.py: add skip status Robert Yang
2017-07-31  9:50 ` [PATCH 04/10] runtime/cases/_ptest.py: " Robert Yang
2017-07-31  9:50 ` [PATCH 05/10] runtime/cases/_ptest.py: rename it to ptest.py Robert Yang
2017-07-31  9:50 ` [PATCH 06/10] utils/logparser.py: fix section check Robert Yang
2017-07-31  9:50 ` [PATCH 07/10] core/target/ssh.py: replace decode errors Robert Yang
2017-07-31  9:50 ` [PATCH 08/10] buildhistory.bbclass: print message when no commit Robert Yang
2017-07-31  9:50 ` [PATCH 09/10] buildhistory.bbclass: add ptest_log Robert Yang
2017-07-31 13:30   ` Paul Eggleton
2017-08-01  1:50     ` Robert Yang
2017-07-31  9:50 ` [PATCH 10/10] testimage.bbclass: update comments Robert Yang
2017-07-31 13:41 ` [PATCH 00/10] Revive ptest and add result to buildhistory Paul Eggleton
2017-08-01  6:47   ` Robert Yang

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.1501494496.git.liezhi.yang@windriver.com \
    --to=liezhi.yang@windriver.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 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.