Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/7] /oeqa/manual/compliance-test: remove obsolete test
Date: Sat, 16 Nov 2019 19:35:14 -0800	[thread overview]
Message-ID: <1573961720-4099-1-git-send-email-akuster808@gmail.com> (raw)

ltpstress was removed in Oct 2018

https://github.com/linux-test-project/ltp/commit/e752f7c19674d9b2f7d37aed123561a3f6410e97#diff-5231627fc8640e0adb955f9e69c3c08d

Remove LTP stress tests
ltpstress.sh runs stress.part[1-3]. But these runtest files just
duplicate definitions:
* stress.part1: fs, mm, nfs
* stress.part2: ipc, math, nptl
* stress.part3: net.multicast, pty, syscalls

The definitions are outdated anyway. There is no point trying
to keep them sync.

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
 meta/lib/oeqa/manual/compliance-test.json | 28 ----------------------------
 1 file changed, 28 deletions(-)
 delete mode 100644 meta/lib/oeqa/manual/compliance-test.json

diff --git a/meta/lib/oeqa/manual/compliance-test.json b/meta/lib/oeqa/manual/compliance-test.json
deleted file mode 100644
index e374c5b..0000000
--- a/meta/lib/oeqa/manual/compliance-test.json
+++ /dev/null
@@ -1,28 +0,0 @@
-[
-  {
-    "test": {
-      "@alias": "compliance-test.compliance-test.stress_test_-_ltp_-Beaglebone",
-      "author": [
-        {
-          "email": "corneliux.stoicescu@intel.com",
-          "name": "corneliux.stoicescu@intel.com"
-        }
-      ],
-      "execution": {
-        "1": {
-          "action": "Build LTP with toolchain or in sdk image",
-          "expected_results": ""
-        },
-        "2": {
-          "action": "Copy LTP folder into target, for example, /opt/ltp. Modify script,  testscripts/ltpstress.sh, set Iostat=1, NO_NETWORK=1",
-          "expected_results": ""
-        },
-        "3": {
-          "action": "cd testscripts/ && ./ltpstress.sh",
-          "expected_results": "This stress case will run for 24 hours Check the result\ntarget should not crash with the program "
-        }
-      },
-      "summary": "stress_test_-_-ltp_-Beaglebone"
-    }
-  }
-]
-- 
2.7.4



             reply	other threads:[~2019-11-17  3:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17  3:35 Armin Kuster [this message]
2019-11-17  3:35 ` [PATCH 2/7] oeqa/manual/bsp-hw: remove rpm -ivh test Armin Kuster
2019-11-17  3:35 ` [PATCH 3/7] oeqa/runtime/boot: add reboot test Armin Kuster
2019-11-17  3:35 ` [PATCH 4/7] oeqa/manual/bsp-hw: remove " Armin Kuster
2019-11-17  3:35 ` [PATCH 5/7] oeqa/manual/bsp-hw: move storage tests to runtime Armin Kuster
2019-11-17  3:35 ` [PATCH 6/7] oeqa/manual/bsp-hw: remove usb and SDmicro tests Armin Kuster
2019-11-17  3:35 ` [PATCH 7/7] manual/bsd-hw: remove bash tests Armin Kuster
2019-11-17  4:02 ` ✗ patchtest: failure for "/oeqa/manual/compliance-test: ..." and 6 more Patchwork

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=1573961720-4099-1-git-send-email-akuster808@gmail.com \
    --to=akuster808@gmail.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