Flent-users discussion archives
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] Re: [tohojo/flent] add test conf files to test results (#224)
Date: Mon, 03 May 2021 04:41:43 -0700	[thread overview]
Message-ID: <tohojo/flent/issues/224/831205743@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/224@github.com>

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

moeller0 ***@***.***> writes:

> Hi Toke,
>
> I just got hold of a flent.gz file from somebody with a new test, and
> my flent can not open that file (makes sense, since the tests is
> unknown). Would it be an option to have the actual test.conf file
> embedded into the flent data, so opening somebody else's test would
> work? It would be very convenient, if not only opening of such files
> would work, but also extraction of the test file to the flent/test
> (unless the test exosts already). But maybe the whole idea has privacy
> issues that doom it?

Yeah, test.conf files are Python code; so no, that should definitely not
be embedded into a data file ;)

The right way to get around this would to make Flent smarter about
parsing out data series and plotting them without having the pre-defined
plots...


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/224#issuecomment-831205743

[-- Attachment #2: Type: text/html, Size: 2008 bytes --]

  reply	other threads:[~2021-05-03 11:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 11:35 [Flent-users] " moeller0
2021-05-03 11:41 ` Toke Høiland-Jørgensen [this message]
2021-05-03 11:54 ` [Flent-users] " moeller0

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

  List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tohojo/flent/issues/224/831205743@github.com \
    --to=notifications@github.com \
    --cc=flent@noreply.github.com \
    --cc=reply+AHVNJP7QAZP6DWT4RLZMOYF6TPBHPEVBNHHDIH5VCU@reply.github.com \
    --cc=subscribed@noreply.github.com \
    --subject='[Flent-users] Re: [tohojo/flent] add test conf files to test results (#224)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox