test suite reviews and discussions
 help / color / mirror / Atom feed
From: Patrick MacArthur <pmacarth@iol.unh.edu>
To: Ali Alnubani <alialnu@mellanox.com>
Cc: "dts@dpdk.org" <dts@dpdk.org>,
	"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>
Subject: Re: [dts] [PATCH for-next v2 4/5] tests/TestSuite_nic_single_core_perf: Use user-specified output dir
Date: Thu, 29 Mar 2018 14:55:58 -0400	[thread overview]
Message-ID: <CABj6NQy7=YkWa8XWs4LejVit-C1qOO6cdwbm0tLe08YT1X5jSQ@mail.gmail.com> (raw)
In-Reply-To: <DB6PR0501MB26309F932F198AAFF5157AB1D7A30@DB6PR0501MB2630.eurprd05.prod.outlook.com>

Hi, Ali,

That was a rebase error which will be fixed in v3.

Thanks,
Patrick

On Wed, Mar 28, 2018 at 12:19 PM, Ali Alnubani <alialnu@mellanox.com> wrote:
> Hi Patrick,
> You are using os module w/o it being imported in this patch.
>
> Thanks,
> Ali
>
>> -----Original Message-----
>> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Patrick MacArthur
>> Sent: Wednesday, March 21, 2018 12:21 AM
>> To: dts@dpdk.org
>> Cc: dpdklab@iol.unh.edu
>> Subject: [dts] [PATCH for-next v2 4/5] tests/TestSuite_nic_single_core_perf:
>> Use user-specified output dir
>>
>> The user can override the default output directory via a command line
>> argument, but this script does not account for that. Fix the script to look up
>> the output directory that the user requested and place the custom output
>> file in that directory.
>>
>> Tested-by: Ali Alnubani <alialnu@mellanox.com>
>> Signed-off-by: Patrick MacArthur <pmacarth@iol.unh.edu>
>> ---
>>  tests/TestSuite_nic_single_core_perf.py | 4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/TestSuite_nic_single_core_perf.py
>> b/tests/TestSuite_nic_single_core_perf.py
>> index 21de93624cb4..bff763c129fa 100644
>> --- a/tests/TestSuite_nic_single_core_perf.py
>> +++ b/tests/TestSuite_nic_single_core_perf.py
>> @@ -41,6 +41,7 @@ from settings import HEADER_SIZE  from pmd_output
>> import PmdOutput  from copy import deepcopy  from prettytable import
>> PrettyTable
>> +import rst
>>
>>  class TestNicSingleCorePerf(TestCase):
>>
>> @@ -244,7 +245,8 @@ class TestNicSingleCorePerf(TestCase):
>>
>> table_row.append(self.test_result[frame_size][descriptor][header[3]])
>>
>> table_row.append(self.test_result[frame_size][descriptor][header[4]])
>>                  table.add_row(table_row)
>> -        file_to_save = open("output/%s_single_core_perf.txt" % self.nic, 'w')
>> +        file_to_save = open(os.path.join(
>> +            rst.path2Result, "%s_single_core_perf.txt" % self.nic),
>> + 'w')
>>          file_to_save.write(str(table))
>>          file_to_save.close()
>>
>> --
>> 2.14.1
>



-- 
Patrick MacArthur
Research and Development, High Performance Networking and Storage
UNH InterOperability Laboratory

  reply	other threads:[~2018-03-29 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 22:20 [dts] [PATCH for-next v2 0/5] Fixes and modifications for T-Rex integration and nic_single_core_perf Patrick MacArthur
2018-03-20 22:20 ` [dts] [PATCH for-next v2 1/5] framework/texttable: Update to latest upstream version Patrick MacArthur
2018-03-20 22:20 ` [dts] [PATCH for-next v2 2/5] framework: Do not attempt ping6 on T-Rex ports Patrick MacArthur
2018-03-20 22:20 ` [dts] [PATCH for-next v2 3/5] tests/TestSuite_nic_single_core_perf: Fix config parsing Patrick MacArthur
2018-03-20 22:20 ` [dts] [PATCH for-next v2 4/5] tests/TestSuite_nic_single_core_perf: Use user-specified output dir Patrick MacArthur
2018-03-28 16:19   ` Ali Alnubani
2018-03-29 18:55     ` Patrick MacArthur [this message]
2018-03-20 22:20 ` [dts] [PATCH for-next v2 5/5] framework/pktgen: Start T-Rex during prepare_generator() Patrick MacArthur

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='CABj6NQy7=YkWa8XWs4LejVit-C1qOO6cdwbm0tLe08YT1X5jSQ@mail.gmail.com' \
    --to=pmacarth@iol.unh.edu \
    --cc=alialnu@mellanox.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=dts@dpdk.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;
as well as URLs for NNTP newsgroup(s).