Hi LAVA mainters,
Nice to meet you.
I want to add my pub key after LAVA installed container.
But I don't which parameters should I need add in my job xx.yaml file.
Could you give me some help and advice.
>>>>>>>>>>>>>>> Some part information of my xx.yaml file: <<<<<<<<<<<<<<<<<<<<<<<<<<
actions:
- deploy:
timeout:
minutes: 300
to: lxc
os: ubuntu
packages: [python, wget, unzip, python-pexpect, python-serial, openssh-server]
- boot:
prompts:
- '[root(a)(.*) /]#'
timeout:
minutes: 300
method: lxc
- test:
timeout:
minutes: 300
gefinitionsg
- run:
steps:
lava-test-shell: echo "------------------------------------- debug 1 -----------------------"
lava-test-shell: wget --no-proxy -q http://otcpkt.bj.intel.com/downloads/pubkey/sys_oak.zip
lava-test-shell: mkdir -p ~/.ssh
lava-test-shell: unzip sys_oak.zip -d ~/.ssh
definitions:
- repository: ssh://sys_oak@git-amr-4.devtools.intel.com:29418/pk_osi_test-source.git
from: git
path: <device>/<test_type>_lxc.yaml
name: <test_type>-<device>
params:
BUILD_NUMBER: <build_number>
IMAGE_URL: <image_url>
PRODUCT: <build_name>
IRC_USER: "sys_oak"
PUB_KEY: "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDCDJvT5UPE***************************
>>>>>>>>>>>>>>> Some part information of my xx.yaml file: <<<<<<<<<<<<<<<<<<<<<<<<<<
Best Regards
Zhanghui Yuan
OTC Production Kernel Integration Test
Hi,
We are doing boot regression test using (in DB{410,820}c) an Android boot
image that contains a ramdisk [1].
We aim to do functional testing in a way that if the basic testing fails
the next test definition dosen't run, that's implies dependencies over
-test entries in the job [2].
Does LAVA test shell provides this kind of functionality?
If not, any idea to achieve this functionality.
Regards,
Anibal
[1] https://validation.linaro.org/scheduler/job/1884978/definition
[2]
https://validation.linaro.org/scheduler/job/1884978/definition#defline117