add test conf files to test results

[moeller0]

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?

[tohojo]

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...

[moeller0]

Ah, thanks, just unzipped the file, and I see what you mean about not including the python code. I had this completely wrong idea, that a flent.gz would be a zipped directory containing a set of different files, not sure why (I must be confusing two different projects her, but I fail to remember what the second is).

By now I got hold of the missing test.conf files, but the next time I encounter this issue I know where to poke/what to do ;)