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, view it on GitHub, or unsubscribe.