From: Saeed <ionictea@gmail.com>
To: fio@vger.kernel.org
Subject: Re: fio2gnuplot issue
Date: Thu, 14 Jul 2016 19:50:44 -0500 [thread overview]
Message-ID: <nm9c13$dsi$1@ger.gmane.org> (raw)
In-Reply-To: CALjAwxjnttcDporW3ep6hi7URVUCnD=GCwdYpmR10DHkQPTfEw@mail.gmail.com
Thanks! I suspected it must've been something with gnuplot because it
seems to work with Ubuntu 15.xx (running Gnuplot 4.xx) and breaks with
Ubuntu 16.xxx (running Gnuplot 5.xx).
I tried contacting Erwan for an answer on a possible update but gotten
no response.
On 2016-07-14 05:22:55 +0000, Sitsofe Wheeler said:
>>
>> On 2016-07-05 21:52:47 +0000, Saeed Tea said:
>>
>>> I'm trying generate graphs with logs create by fio using fio2gnu and keep
>>> getting this error when generating graphs for iops or bandwidth:
>>>
>>> 1 files Selected with pattern '*_iops.log'
>>> |-> 4k.results_iops.log
>>>
>>> Running gnuplot Rendering
>>> "/usr/share/fio//math.gpm", line 25: no datablock named $1
>>>
>>> "/usr/share/fio//graph2D.gpm", line 25: no datablock named $1
>>>
>>>
>>> Rendering traces are available in the current directory
>>>
>>> Checking the directory listing only shows this file:
>>>
>>> $3.png
>>>
>>> Am I missing something in fio profile?? Here's a snippet:
>
> This happens because you have gnuplot 5 and it dropped support for the
> $1 way of passing arguments on the command line (see
> http://stackoverflow.com/a/31815067/4513656 ). To get around this both
> the .gpm and and fio2gnuplot would have to be rewritten to use a
> different means of passing parameters in. I'm not sure any method
> beyond using environment variables would work for both old and new
> versions of gnuplot...
>
> CC'ing the original author of fio2gnuplot for comment.
next prev parent reply other threads:[~2016-07-15 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 21:52 fio2gnuplot issue Saeed Tea
2016-07-05 22:09 ` Saeed Tea
2016-07-14 5:22 ` Sitsofe Wheeler
2016-07-14 5:27 ` Sitsofe Wheeler
2016-07-15 0:50 ` Saeed [this message]
2016-07-17 8:47 ` Sitsofe Wheeler
2016-07-21 15:55 ` Saeed
2016-07-21 20:01 ` Sitsofe Wheeler
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='nm9c13$dsi$1@ger.gmane.org' \
--to=ionictea@gmail.com \
--cc=fio@vger.kernel.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