rlFileSubmit should copy files to TMT_PLAN_DATA in case of tmt about beakerlib HOT 5 CLOSED

The beakerlib is primarily focused on the beaker and so it checks beaker-like variables. The tmt sets the respective beaker-like variables if the test framework is set to beakerlib. Does your test specify the beakerlib framework?
AFAIK, tmt should be covering it already. @psss, @lukaszachy can you confirm that?

from beakerlib.

rlFileSubmit copies to TMT_TEST_DATA.

which is not set/available in prepare or finish steps

from beakerlib.

Once, I confused myself by forgetting the beakerlib framework which caused good behavior at first glance yet weird at better look due to missing env. variables and results handling.

from beakerlib.

To be more precise: for 'beakerlib' framework tmt sets BEAKERLIB_DIR and BEAKERLIB_COMMAND_SUBMIT_LOG variables. The later point to tmt-file-submit script which uses 'TMT_TEST_DATA' variable as location to put any files in.

IMO there is no need for beakerlib to be aware of 'tmt' or any other executors, there is already plenty of variables to set if necessary.

@pellecchialuigi Could you be more verbose about your use case which lead to this issue? All what I can think of is teemtee/tmt#969

from beakerlib.

Hi all, and sorry for the late feedback. I'm running some beakerlib based tests with tmt and I had to access some artifacts that were handled with the rlFileSubmit. I wasn't aware about the integration from the tmt side, I was looking in something inside the beakerlib code. As long as tmt allow to retrieve the artifacts I think we can close this issue.
Thanks both for your kind support and all the explainations.

from beakerlib.