Test Job Requests comparison

From eLinux.org
Revision as of 09:50, 27 March 2019 by Tim Bird (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Different systems manage job requests differently

Linaro job definition YAML file

Here is a job definition file for LAVA: (obtained from https://validation.linaro.org/static/docs/v2/dispatcher-format.html)

device_type: kvm

job_name: kvm-pipeline
job_timeout:
  minutes: 15            # timeout for the whole job (default: ??h)
action_timeout:
  minutes: 5         # default timeout applied for each action; can be overriden in the action itself (default: ?h)
priority: medium

actions:

   - deploy:
       timeout:
         minutes: 20
       to: tmpfs
       images:
         rootfs:
           url: https://images.validation.linaro.org/kvm/standard/stretch-2.img.gz
           image_arg: -drive format=raw,file={rootfs}
           compression: gz

   - boot:
       method: kvm
       media: tmpfs
       failure_retry: 2
       prompts:
         - 'linaro-test'
         - 'root@debian:~#'

   - test:
       failure_retry: 3
       name: kvm-basic-singlenode  # is not present, use "test $N"
       timeout:
         minutes: 5 # uses install:deps, so takes longer than singlenode01
       definitions:
           - repository: git://git.linaro.org/lava-team/lava-functional-tests.git
             from: git
             path: lava-test-shell/smoke-tests-basic.yaml
             name: smoke-tests
           - repository: https://git.linaro.org/lava-team/lava-functional-tests.git
             from: git
             path: lava-test-shell/single-node/singlenode03.yaml
             name: singlenode-advanced

Note that this has actions: deploy, boot, test