New issue
Advanced search Search tips

Issue 914182 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Version negotiation between the tast command and local_test_runner

Project Member Reported by nya@chromium.org, Dec 12

Issue description

We want some version negotiation mechanism between tast and local_test_runner.

For example, we recently introduced a new external data file mechanism (Issue 900181), and semenzato@ was caught by a version difference between the two. In particular, local_test_runner was old so *.external files pushed from host to DUT was not recognized, ending up "data file not found" errors.

 
I've tried to avoid adding explicit versioning between tast and local_test_runner so far. I agree that we need to maintain some degree of compatibility in both directions, although I haven't thought about an explicit time window.

Ideally, newer versions of the "tast" command should continue to work with fairly-old versions of local_test_runner. This lets developers run tests on older system images.

I'm less sure about the other direction, where the DUT has a newer version of local_test_runner. Maybe we need to be more aggressive about telling developers to emerge tast-cmd? Right now, does that only happen when the chroot is updated in response to build_packages being run?

Sign in to add a comment