test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Mei, JianweiX" <jianweix.mei@intel.com>
To: "Zhao, HaiyangX" <haiyangx.zhao@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhao, HaiyangX" <haiyangx.zhao@intel.com>
Subject: Re: [dts] [PATCH V1] conf/test_case_checklist: update 32bit unsupported	cases
Date: Thu, 30 Apr 2020 06:08:42 +0000	[thread overview]
Message-ID: <312CE835782EEA45A2358F01A9B74B303F7449@CDSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <1588225698-139616-1-git-send-email-haiyangx.zhao@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]

Tested-by:  Mei Jianwei <jianweix.mei@intel.com>

-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Haiyang Zhao
Sent: Thursday, April 30, 2020 1:48 PM
To: dts@dpdk.org
Cc: Zhao, HaiyangX <haiyangx.zhao@intel.com>
Subject: [dts] [PATCH V1] conf/test_case_checklist: update 32bit unsupported cases

*.flags/qinq_packet_filter_VF_queues are unsupported
  in 32bit OS due to address space limited.

Signed-off-by: Haiyang Zhao <haiyangx.zhao@intel.com>
---
 conf/test_case_checklist.json | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index 0434f07..2e0a081 100644
--- a/conf/test_case_checklist.json
+++ b/conf/test_case_checklist.json
@@ -1988,6 +1988,40 @@
             "Comments": ""
         }
     ],
+    "flags": [
+        {
+            "OS": [
+                "ALL"
+            ],
+            "NIC": [
+                "ALL"
+            ],
+            "Target": [
+                "i686-native-linuxapp-gcc",
+                "i686-native-linuxapp-icc",
+                "i686-native-linuxapp-clang"
+            ],
+            "Bug ID": "",
+            "Comments": "32 bit address space limited"
+        }
+    ],
+    "qinq_packet_filter_VF_queues": [
+        {
+            "OS": [
+                "ALL"
+            ],
+            "NIC": [
+                "ALL"
+            ],
+            "Target": [
+                "i686-native-linuxapp-gcc",
+                "i686-native-linuxapp-icc",
+                "i686-native-linuxapp-clang"
+            ],
+            "Bug ID": "",
+            "Comments": "32 bit address space limited"
+        }
+    ],
     "multiprocess": [
         {
             "OS": [
--
2.18.2


[-- Attachment #2: TestUnitTestsEal.log --]
[-- Type: application/octet-stream, Size: 445 bytes --]

01/05/2020 01:30:33                            dts: 
TEST SUITE : TestUnitTestsEal
01/05/2020 01:30:33                            dts: NIC :        fortville_25g
01/05/2020 01:30:33             dut.10.240.183.216: 
01/05/2020 01:30:33                         tester: 
01/05/2020 01:30:33               TestUnitTestsEal: Test Case test_flags Result SKIPPED:
01/05/2020 01:30:33                            dts: 
TEST SUITE ENDED: TestUnitTestsEal

[-- Attachment #3: TestQinqFilter.log --]
[-- Type: application/octet-stream, Size: 131566 bytes --]

  reply	other threads:[~2020-04-30  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  5:48 Haiyang Zhao
2020-04-30  6:08 ` Mei, JianweiX [this message]
2020-05-06  3:28 ` Tu, Lijuan

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=312CE835782EEA45A2358F01A9B74B303F7449@CDSMSX102.ccr.corp.intel.com \
    --to=jianweix.mei@intel.com \
    --cc=dts@dpdk.org \
    --cc=haiyangx.zhao@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).