Flasher is the name we gave to the custom deploy method that will call our internal programmer.
Denis
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: mardi 22 janvier 2019 11:45 To: Denis HUMEAU denis.humeau@st.com Cc: Remi Duraffort remi.duraffort@linaro.org; lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] Piece of advice to combine interactive boot and Linux testing
On Tue, 22 Jan 2019 at 10:32, Denis HUMEAU denis.humeau@st.com wrote:
Thanks for quick reply.
Sorry, I'm a bit confused. In my initial job (skeleton below), I already had a deploy (custom), and no namespace.
I looked at the original job you posted. What is 'flasher'? - deploy: to: flasher I didn't find it in the lava docs. But looking at the whole job it looks like sth external to the board. In this case you need to separate 'flasher' actions to separate namespace and board testing actions to a different one.
milosz
Rémi, are your latest patches sufficient to succeed in combining interactive and kernel test without rebooting in between?
Denis
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: mardi 22 janvier 2019 11:25 To: Remi Duraffort remi.duraffort@linaro.org Cc: Denis HUMEAU denis.humeau@st.com; lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] Piece of advice to combine interactive boot and Linux testing
On Tue, 22 Jan 2019 at 10:11, Remi Duraffort remi.duraffort@linaro.org wrote:
- test: timeout: minutes: 20 interactive: - name: firmware prompts: ['=>'] script: - command: env print name: command1 - command: env print name: command 2 - command: env print name: command 3 - command: env print name: command 4 - command: run bootcmd name: start_kernel patterns: - message: "login: root (automatic login)" result: successsyntax is wrong here, but when fixed this should work. Please check here: https://staging.validation.linaro.org/scheduler/job/247775/defini ti on
What I tried didn't actually work. Here is a job: https://staging.validation.linaro.org/scheduler/job/247794/definiti on
LAVA reports it's missing all it's helpers. That is pretty obvious as there was no 'deploy to fastboot' stage. I tried adding it but than LAVA complains that 'namespace' and 'interactive' test don't work together. @Remi could you take a look?
1/ namespace are now available for interactive tests too (missing parameter in the schema validator): https://git.lavasoftware.org/lava/lava/commit/c0eeb4b28fda334b432057 2d bb0b1ac3bfc9cdd7 2/ adding another deploy stage with the right namespace as suggested by milosz should work
Yay, this works. Thank you for a quick fix! https://staging.validation.linaro.org/scheduler/job/247927
milosz
-- Rémi Duraffort LAVA Team, Linaro