There are a few mistakes in this job: 1. move context section to the top 2. make sure you have only one 'actions' section 3. make sure you have a namespace in each action.

That should at least fix problems with job validation. I've never booted android with qemu so I've no idea how that works. How does it expose 'usb like' device for adb connection? In other words if you use qemu outside of LAVA to boot and test android, how do you start VTS/CTS?

milosz

On Wed, 14 Aug 2019 at 12:56, George Nistor george.n@l4b-software.com wrote:

Hi Milosz, Thanks for the answer.

I am using your example you gave me few days ago, and just replace the target section. (I know the test are for pie and the iso is android 8.1) but what I want now is to know how to define the target qemu with android on it.

Here is the job:

device_type: qemu job_name: question_to_Linaro_1 priority: medium visibility: public timeouts: job: minutes: 360 action: minutes: 15 connection: minutes: 2 protocols: lava-lxc: name: lxc-test distribution: ubuntu release: xenial arch: amd64 verbose: true actions:

• deploy: namespace: tlxc timeout: minutes: 10 to: lxc packages:
  • wget
  • unzip
  • git
  • trace-cmd
  os: ubuntu
• boot: namespace: tlxc prompts:
  • root@(.*):/#
  • :/
  timeout: minutes: 5 method: lxc
• test: namespace: tlxc timeout: minutes: 10 definitions:
  • repository: https://git.linaro.org/qa/test-definitions.git from: git path: automated/linux/android-platform-tools/install.yaml name: install-android-platform-tools-r2800 parameters: LINK: https://dl.google.com/android/repository/platform-tools_r28.0.0-linux.zip

# CONTEXT_BLOCK context: arch: amd64 # ACTIONS_BLOCK actions:

• deploy: timeout: minutes: 120 to: iso-installer images: rootfs: url: https://osdn.net/frs/redir.php?m=cznic&f=android-x86%2F69704%2Fandroid-x... sha256sum: 71e3cd7e7151fbc7e9bb29be10e337b2545586d3ef173c5ae8c07d13bf595732

# BOOT_BLOCK

• boot: method: qemu-iso media: media=cdrom,readonly timeout: minutes: 20 connection: serial
• test: namespace: tlxc connection: lxc timeout: minutes: 100 definitions:
  • from: inline path: android-boot.yaml name: android-boot repository: metadata: format: Lava-Test Test Definition 1.0 name: android-boot description: android-boot run: steps: - lava-test-case "android-boot-wait-for-device" --shell adb wait-for-device - lava-test-case "android-boot-sleep-2mins" --shell adb shell sleep 120 - lava-test-case "android-boot" --shell adb shell getprop sys.boot_completed
• test: namespace: tlxc connection: lxc timeout: minutes: 360 definitions:
  • repository: https://git.linaro.org/qa/test-definitions.git from: git path: automated/android/noninteractive-tradefed/tradefed.yaml params: TEST_PARAMS: cts-lkft --disable-reboot TEST_URL: http://people.linaro.org/~yongqin.liu/lkft/pie/cts/9.0_r7//android-cts.zip TEST_PATH: android-cts RESULTS_FORMAT: atomic ANDROID_VERSION: android-9.0.0_r34 name: cts-lkft

---

From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: Wednesday, August 14, 2019 2:43 PM To: George Nistor george.n@l4b-software.com Cc: lava-users@lists.lavasoftware.org lava-users@lists.lavasoftware.org Subject: Re: running CTS and VTS from lxc against an qemu target with AOSP

George,

I don't see any LXC part in this job. Could you share the full job definition?

milosz

On Wed, 14 Aug 2019 at 12:40, George Nistor george.n@l4b-software.com wrote:

...

Hi Lava Users,

I am trying to create a target with qemu running android as an ISO image. The job I intend to write is to run CTS and VTS on a qemu target with android. But I receive error when submitting.

Could anyone help me telling me which are my mistakes I do with the job?

None of the deployment strategies accepted your deployment parameters, reasons given: qemu-nfs: "to" is not "nfs" lxc: "to" parameter is not "lxc" overlay: 'overlay' not in the device configuration deploy methods removeable: "media" was not "sata", "sd", or "usb" fastboot: "to" parameter is not "fastboot" tftp: "to" parameter is not "tftp" nfs: "to" parameter is not "nfs" images: "to" parameter is not "tmpfs" flasher: 'flasher' not in the device configuration deploy methods docker: 'docker' not in the device configuration deploy methods uboot-ums: "to" parameter is not "u-boot-ums" ssh: "ssh" is not in the device configuration deploy methods download: "to" parameter is not "download" iso: "iso" was not in the parameters recovery-mode: 'recovery' not in the device configuration deploy methods mps: "mps" was not in the device configuration deploy methods nbd: "to" parameter is not "nbd" vemsd: "to" parameter is not "vemsd"

device_type: qemu job_name: george_ISO_6 timeouts: job: minutes: 120 action: minutes: 120 connection: minutes: 120 priority: medium visibility: public # CONTEXT_BLOCK context: arch: amd64 # ACTIONS_BLOCK actions:

• deploy: timeout: minutes: 120 to: iso-installer images: rootfs: url: https://osdn.net/frs/redir.php?m=cznic&f=android-x86%2F69704%2Fandroid-x... sha256sum: 71e3cd7e7151fbc7e9bb29be10e337b2545586d3ef173c5ae8c07d13bf595732

# BOOT_BLOCK

• boot: method: qemu-iso media: media=cdrom,readonly timeout: minutes: 20 connection: serial