Re: oeqa: testcase caching

Richard Purdie

On Mon, 2021-01-04 at 11:44 +0100, Konrad Weihmann wrote:
I have a bunch of custom testcases (oeqa/runtime/cases) which are
interacting with "d" from the build host - basically fetching some
while executing the test, e.g.

foo =['MY_CUSTOM_VAR']

What I've seen is that these files create python __pycache__ files
during parsing of the testimage run.

On the initial run everything is working like expected, but if I now
change the variable "MY_CUSTOM_VAR", without modifying the
target-filesystem the value inside the test case doesn't get updated.

Did anyone else encountered this?

To me it seems like the value of the var does make it into the
files, ignoring the updated value on a second run.

On that note: wouldn't it make sense to disable the cache creation
oeqa test cases? just to mitigate chances of such scenarios?

Or maybe I'm doing something wrong here, so any pointers are highly
FWIW this doesn't sound right to me. pyc files (in __pycache__) would
cache the code, not data so I don't see how these values would be
preserved there. I don't doubt you're seeing some kind of issue but I
suspect its more likely bitbake's cache or something...



Join to automatically receive all group messages.