Using custom tests in the LAVA farm is not documented

[Marcin Juszkiewicz]

I have a test which I like to run on LAVA farm. But after checking all documentation available at http://lava.rtfd.org/ I do not see a way to do it.

This part should have documentation cause it may be more and more used by other users. Running tests locally with 'lava-test' is not always possible due to lack of ARM hardware or other use of available one.

[Zygmunt Krynicki (zyga)]

We should document this in the dispatcher documentation. Alternatively we should have a task-oriented part of the global documentation that focuses on users wanting to use the infrastructure we provide

[Marcin Juszkiewicz (hrw)]

Let me clarify.

I have a test definition locally which I used locally (with lava-test) and it works fine. But from all documentation about lava which I got that on lava farm I can run only your tests (so mine is not possible).

And I plain shell inside of job description (which I would use to skip 'lets find out how to add own test') is not possible.

[Marcin Juszkiewicz (hrw)]

This test requires extra PPA and 'gcc-linaro' from it.

[Marcin Juszkiewicz (hrw)]

This is a job definition which adds PPA, installs 'gcc-linaro' from it and then runs test.

[Marcin Juszkiewicz (hrw)]

For those which find a bug:

The key is to write test and put it somewhere in internet (available by http is best). Then in job description you have to register test:

 {
  "command": "lava_test_install",
  "parameters": {
   "tests": [
    "gcc-linaro-build-test"
    ],
   "register": [
    "http://people.linaro.org/~hrw/lava/job-gcc-linaro-build-test.json"
    ],
    "timeout": 7200
  }
 },

And then you should be able to use it.

[Ricardo Salveti (rsalveti)]

There's an example for out-of-tree tests at https://wiki.linaro.org/Platform/Validation/LAVA/SubmittingTests, but I agree it'd be good to improve it, explaining better the possible variables and results.