All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bird, Timothy" <Tim.Bird@sony.com>
To: "dhinakar.k@samsung.com" <dhinakar.k@samsung.com>,
	"fuego@lists.linuxfoundation.org"
	<fuego@lists.linuxfoundation.org>
Subject: Re: [Fuego] Benchmark.Stream fails with ValueError: invalid literal for float() on x86 64-bit target
Date: Fri, 6 Oct 2017 15:14:59 +0000	[thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF3AD20E24@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <20171006122701epcms5p115d5690dd88aa15273c67b843bc0db04@epcms5p1>



> -----Original Message-----
> From: fuego-bounces@lists.linuxfoundation.org [mailto:fuego-
> bounces@lists.linuxfoundation.org] On Behalf Of Dhinakar Kalyanasundaram
> Sent: Friday, October 06, 2017 5:27 AM
> To: fuego@lists.linuxfoundation.org
> Subject: [Fuego] Benchmark.Stream fails with ValueError: invalid literal for
> float() on x86 64-bit target
> 
> Hi,
> 
> 
> 
> Benchmark.Stream fails with ValueError: invalid literal for float() on x86 64-bit
> target.
> 
> The execution log has been pasted below for reference.
> 
> Please let me know how it can be fixed. Thanks in advance.

This is fixed in my 'next' branch with the following commit.

https://bitbucket.org/tbird20d/fuego-core/commits/b175ddb18094b2639ee31272a275f79cd7d81434


Please do a 'git pull' to an appropriate fuego-core repository on your host, and
let me know if it fixes it for you.
 -- Tim

> ##### doing fuego phase: build ########
> The test is already built
> Fuego test_build duration=0 seconds
> ##### doing fuego phase: deploy ########
> ##### doing fuego phase: pre_deploy ########
> ##### doing fuego phase: test_deploy ########
> ##### doing fuego phase: post_deploy ########
> ##### doing fuego phase: run ########
> WARNING: test log file parameter empty, so will use default
> -------------------------------------------------------------
> STREAM version $Revision: 5.9 $
> -------------------------------------------------------------
> This system uses 8 bytes per DOUBLE PRECISION word.
> -------------------------------------------------------------
> Array size = 2000000, Offset = 0
> Total memory required = 45.8 MB.
> Each test is run 10 times, but only
> the *best* time for each is used.
> -------------------------------------------------------------
> Printing one line per active thread....
> -------------------------------------------------------------
> Your clock granularity/precision appears to be 1 microseconds.
> Each test below will take on the order of 2795 microseconds.
>    (= 2795 clock ticks)
> Increase the size of the arrays if this shows that
> you are not getting at least 20 clock ticks per test.
> -------------------------------------------------------------
> WARNING -- The above is only a rough guideline.
> For best results, please be sure you know the
> precision of your system timer.
> -------------------------------------------------------------
> Function      Rate (MB/s)   Avg time     Min time     Max time
> Copy:        8328.7451       0.0039       0.0038       0.0040
> Scale:       7978.2279       0.0040       0.0040       0.0041
> Add:         8857.6969       0.0055       0.0054       0.0057
> Triad:       9012.3368       0.0054       0.0053       0.0054
> -------------------------------------------------------------
> Solution Validates
> -------------------------------------------------------------
> ##### doing fuego phase: post_test ########
> Teardown board link
> ##### doing fuego phase: processing ########
> running python with
> PATH=/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/gam
> es
> Reading current values from /fuego-rw/logs/Benchmark.Stream/TRAV-
> Ethernet-x86.default.2.2/testlog.txt
> Traceback (most recent call last):
>   File "/fuego-core/engine/tests/Benchmark.Stream/parser.py", line 24, in
> <module>
>     sys.exit(plib.process_data(ref_section_pat, cur_dict, 's', 'Rate, MB/s'))
>   File "/fuego-core/engine/scripts/parser/common.py", line 600, in
> process_data
>     new_measure = {"name":measure, "measure": float(value)}
> ValueError: invalid literal for float(): 9012.3368 0.0054

This was caused by a bug in the parser.py for this test.

> ERROR: results did not satisfy the threshold
> Fuego: all test phases complete!
> Build step 'Execute shell' marked build as failure
> [description-setter] Description set:  <a
> href="/storm/userContent/fuego.logs/Benchmark.Stream/TRAV-Ethernet-
> x86.default.2.2/testlog.txt">testlog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.Stream/TRAV-Ethernet-
> x86.default.2.2/run.json">run.json</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.Stream/TRAV-Ethernet-
> x86.default.2.2/consolelog.txt">fuegolog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.Stream/TRAV-Ethernet-
> x86.default.2.2/devlog.txt">devlog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.Stream/TRAV-Ethernet-
> x86.default.2.2/prolog.sh">prolog.sh</a>
> Finished: FAILURE
>

  reply	other threads:[~2017-10-06 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20171006122701epcms5p115d5690dd88aa15273c67b843bc0db04@epcms5p1>
2017-10-06 12:27 ` [Fuego] Benchmark.Stream fails with ValueError: invalid literal for float() on x86 64-bit target Dhinakar Kalyanasundaram
2017-10-06 15:14   ` Bird, Timothy [this message]
     [not found]   ` <CGME20171006122701epcms5p115d5690dd88aa15273c67b843bc0db04@epcms5p3>
2017-10-06 15:18     ` Dhinakar Kalyanasundaram
2017-10-06 15:28       ` Bird, Timothy

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=ECADFF3FD767C149AD96A924E7EA6EAF3AD20E24@USCULXMSG01.am.sony.com \
    --to=tim.bird@sony.com \
    --cc=dhinakar.k@samsung.com \
    --cc=fuego@lists.linuxfoundation.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.