From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bugzilla@dpdk.org>
Received: by dpdk.org (Postfix, from userid 33)
 id 4B4CC1B117; Tue, 11 Dec 2018 21:34:22 +0100 (CET)
From: bugzilla@dpdk.org
To: ci@dpdk.org
Date: Tue, 11 Dec 2018 20:34:22 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: lab
X-Bugzilla-Component: UNH infra
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: critical
X-Bugzilla-Who: jplsek@iol.unh.edu
X-Bugzilla-Status: CONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: High
X-Bugzilla-Assigned-To: ci@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-122-149-wI3z1YhqOd@http.bugs.dpdk.org/>
In-Reply-To: <bug-122-149@http.bugs.dpdk.org/>
References: <bug-122-149@http.bugs.dpdk.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
Subject: [dpdk-ci] [Bug 122] Performance results are not correct on Intel
 I40E environments
X-BeenThere: ci@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK CI discussions <ci.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/ci>,
 <mailto:ci-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/ci/>
List-Post: <mailto:ci@dpdk.org>
List-Help: <mailto:ci-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/ci>,
 <mailto:ci-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2018 20:34:22 -0000

https://bugs.dpdk.org/show_bug.cgi?id=3D122

--- Comment #1 from Jeremy Plsek (jplsek@iol.unh.edu) ---
I ran this manually, and it had passing results for me.

This is how I tested it (after stopping the CI from running on the node
temporarily):

In one terminal:
cd /root/test_harness/trex-core-2.26/scripts
./t-rex-64 -i --no-scapy-server --cfg ../../trex_cfg.yaml

In another terminal:
cd /root/test_harness/dts
./dts -s --snapshot /tmp/dpdktest2/dpdk.tar.gz # tarball with the patch app=
lied
using commit b0aa225b45 as a baseline for the expected results from
conf/nic_single_core_perf.cfg

Then looking at the output folder logs, it had similar results to the email.


How did you test this? What baseline did you use? How did you make the tarb=
all
that was being tested?

--=20
You are receiving this mail because:
You are the assignee for the bug.=