Hello,

you should remove the "os" field in the deploy action.


Cheers

Le mar. 21 mai 2019 à 17:13, Pete Dyer <Pete.Dyer@arm.com> a écrit :
I tried setting this but it gets ignored. Instead, the value in deployment_data.py is used. There is a comment in action.py get_constant() that indicates that while it is supported deployment_data will be used.


When is the removal of support for deployment_data expected? I don't want to invest the time making it work now if I have to change it again in the near future.


Thanks.
Pete





From: Remi Duraffort <remi.duraffort@linaro.org>
Sent: 20 May 2019 10:09
To: Milosz Wasilewski
Cc: Hussin, Mohamad Noor Alim; lava-users@lists.lavasoftware.org; Pete Dyer
Subject: Re: [Lava-users] Using transfer overlay
 
Hello,

in the job definition context, you should define the lava_test_results_dir variable:

==========
context:
  lava_test_results_dir: "/scratch/lava-%s"
==========


Cheers

Le lun. 20 mai 2019 à 10:42, Milosz Wasilewski <milosz.wasilewski@linaro.org> a écrit :
On Mon, 20 May 2019 at 09:35, Hussin, Mohamad Noor Alim
<mohamad.noor.alim.hussin@intel.com> wrote:
>
> I think you can change the path of 'lava_test_dir' and 'lava_test_results_dir' in
>
> lava-dispatcher:/usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py.
>
>
>
> You need to change the for each dispatcher to meet your need. But it is not a good way to do it as it will affect all of the lava job later.

These variables were possible to set in the job context some time ago.
Not sure if it's still possible but worth to try. If not I would
consider this as a bug in LAVA.

milosz

>
>
>
> Regards,
>
> Alim Hussin
>
>
>
> From: Pete Dyer [mailto:Pete.Dyer@arm.com]
> Sent: Monday, May 20, 2019 4:03 PM
> To: Hussin, Mohamad Noor Alim <mohamad.noor.alim.hussin@intel.com>; lava-users@lists.lavasoftware.org
> Subject: Re: Using transfer overlay
>
>
>
> That is what I have in my transfer overlay command.
>
>
>
>     transfer_overlay:
>
>       download_command:  sleep 10 ; ifconfig ; wget
>
>       unpack_command: tar -C /scratch -xzf
>
>
>
> (previously tthe unpack command was "tar -C / -xzf"
>
>
>
> The problem I have is that when the tests get launched it attempts to run
>
> "/lava-10473/bin/lava-test-runner /lava-10473/1"
>
>
>
> But we have unpacked into /scratch so the script cannot be found.
>
>
>
> Pete
>
>
>
>
>
>
>
> ________________________________
>
> From: Hussin, Mohamad Noor Alim <mohamad.noor.alim.hussin@intel.com>
> Sent: 20 May 2019 08:33
> To: Pete Dyer; lava-users@lists.lavasoftware.org
> Subject: RE: Using transfer overlay
>
>
>
> Hi Pete,
>
>
>
> How do you transfer the overlay?
>
> This is an example of snipped code for boot block from LAVA job definition. I think just change the tar command at unpack_command:
>
> - boot:
>
>     timeout:
>
>       minutes: 10
>
>     method: ssh
>
>     prompts:
>
>       - 'root@intel-corei7-64-64:~#'
>
>     transfer_overlay:
>
>       download_command: wget
>
>       unpack_command: tar -C /scratch -xvpf
>
>
>
> Regards,
>
> Alim Hussin
>
>
>
> From: Lava-users [mailto:lava-users-bounces@lists.lavasoftware.org] On Behalf Of Pete Dyer
> Sent: Friday, May 17, 2019 11:26 PM
> To: lava-users@lists.lavasoftware.org
> Subject: [Lava-users] Using transfer overlay
>
>
>
> Hello,
>
>
>
> I'm using transfer overlay to get a set of tests onto the target.
>
>
>
> However I want to untar it into /scratch instead of / because of storage requirements.
>
>
>
> This I can do quite easily.
>
>
>
> However the tests are going to try to run from / (e.g. /lava-10473/bin/lava-test-runner /lava-10473/1)
>
>
>
> Is there a way of running tests from /scratch/lava-10473.... ?
>
>
>
> Or a way of defining a command to run immediately after the transfer overlay that makes a link between /lava-10473 and /scratch/lava-10473 ?
>
>
>
> Thanks.
>
> Pete
>
>
>
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>
> _______________________________________________
> Lava-users mailing list
> Lava-users@lists.lavasoftware.org
> https://lists.lavasoftware.org/mailman/listinfo/lava-users

_______________________________________________
Lava-users mailing list
Lava-users@lists.lavasoftware.org
https://lists.lavasoftware.org/mailman/listinfo/lava-users


--
Rémi Duraffort
LAVA Team, Linaro
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________
Lava-users mailing list
Lava-users@lists.lavasoftware.org
https://lists.lavasoftware.org/mailman/listinfo/lava-users


--
Rémi Duraffort
LAVA Team, Linaro