Hi, Remi,
You said:
> lava-master is receiving an invalid zmq message. I guess you are not using
encryption? Are you fuzzing it?
Sorry, I did not catch you. What does fuzzing it mean? I did not do anything special for LAVA.
Meanwhile, what does "not using encryption" mean? Is this a LAVA master configure item or something else? I did not change anything related to this.
And as I said, it could work ok for some a period, then I leave the whole environment there, no touch for anything. Then severial days later, it may encountered the issue.
BTW, even such things happen, why no a exception handing in LAVA to ignore such issue? Currently it just close the zeromq connection.
------------------------------------------------------------------
Sent At:2019 Oct. 15 (Tue.) 00:25
Subject:Lava-users Digest, Vol 14, Issue 10
Send Lava-users mailing list submissions to
lava-users@lists.lavasoftware.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.lavasoftware.org/mailman/listinfo/lava-users
or, via email, send a message with subject or body 'help' to
lava-users-request@lists.lavasoftware.org
You can reach the person managing the list at
lava-users-owner@lists.lavasoftware.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lava-users digest..."
Today's Topics:
1. Re: lava job without any flashing on a real device (George Nistor)
2. Re: Unexpected crash. (Remi Duraffort)
3. Re: repeat in lava not work (Diego Russo)
----------------------------------------------------------------------
Message: 1
Date: Mon, 14 Oct 2019 13:17:55 +0000
From: George Nistor <george.n@l4b-software.com>
To: "lava-users@lists.lavasoftware.org"
<lava-users@lists.lavasoftware.org>
Subject: Re: [Lava-users] lava job without any flashing on a real
device
Message-ID:
<VI1PR01MB38711749B69B27E8410ABB41F0900@VI1PR01MB3871.eurprd01.prod.exchangelabs.com>
Content-Type: text/plain; charset="utf-8"
Yes,
In my case the only way I could make lava to see the fastboot device was via
running pre-power-command, and I run a script (I customized device descriptor to run a this script as pre-power-command) which does:
1. Power Off
Wait 5s
2.Power On
Wait 30s
3. Login as root
Wait 5s
4. echo reboot bootloader. # make it go in fastboot mode
Immediately after this script runs, the udev rule is triggered and device id added (seen from Lava).
Otherwise the reboot does not work for me.
The line:
nice lxc-attach -n lxc-hikey-test-186 -- fastboot -s xxxxxxx reboot
gives timeout.
Because the device is not seen.
To make the job work without any flashing I removed the
- deploy section which does flashing entirely
For my case:
I have added to boot this section
protocols:
lava-lxc:
- action: fastboot-boot
request: pre-power-command
timeout:
minutes: 5
george
The full job I cannot post due to company policy with confidentiality on projects.
-----Original Message-----
From: Milosz Wasilewski <milosz.wasilewski@linaro.org>
Sent: luni, 14 octombrie 2019 15:58
To: George Nistor <george.n@l4b-software.com>
Subject: Re: lava job without any flashing on a real device
Could you send the question to ML? I don't know why adb is not enough.
Maybe LAVA waits for udev event?
milosz
On Mon, 14 Oct 2019 at 13:51, George Nistor <george.n@l4b-software.com> wrote:
>
> I have managed after all to do it with a job like this:
> My problem was to be able to run pre-power-command before boot, to make lava to see the fastboot device - trigger that python script lxc-device-add.
>
>
> -----Original Message-----
> From: Milosz Wasilewski <milosz.wasilewski@linaro.org>
> Sent: Monday, October 14, 2019 15:02
> To: George Nistor <george.n@l4b-software.com>
> Subject: Re: lava job without any flashing on a real device
>
> There was a feature called 'dummy deploy' but I can't find it any more. Did you try simply removing 'deploy' action? This should do the trick but you will need transfer_overlay in your boot section.
>
> milosz
>
> On Mon, 14 Oct 2019 at 12:33, George Nistor <george.n@l4b-software.com> wrote:
> >
> > Hi Milosz,
> >
> >
> >
> > I have a small question:
> >
> > Is it possible to run a lava job without any deploy – flashing sequence on a real device?
> >
> >
> >
> > I attach the job I’m working on.
> >
> >
> >
> > george
------------------------------
Message: 2
Date: Mon, 14 Oct 2019 15:34:24 +0200
From: Remi Duraffort <remi.duraffort@linaro.org>
To: cnspring2002 <cnspring2002@aliyun.com>
Cc: lava-users <lava-users@lists.lavasoftware.org>
Subject: Re: [Lava-users] Unexpected crash.
Message-ID:
<CANJfhHchH1UZOy=ScC5CUnPkZ55yi3QXrNPqqjk6wSJBFZbrzg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello,
lava-master is receiving an invalid zmq message. I guess you are not using
encryption? Are you fuzzing it?
Le lun. 14 oct. 2019 à 11:18, cnspring2002 <cnspring2002@aliyun.com> a
écrit :
> Hi, Sometimes, lava master will show next error, then seems zemomq crash,
> do you know what's the potential cause?
>
> 2019-08-20 09:14:39,576 DEBUG lava-worker-1 => PING(20)
> 2019-08-20 09:14:39,578 DEBUG lava-worker-2 => PING(20)
> 2019-08-20 09:14:39,580 DEBUG lava-worker-3 => PING(20)
> 2019-08-20 09:14:44,467 ERROR [CLOSE] Unknown exception raised, leaving!
>
> 2019-08-20 09:14:44,467 ERROR 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte
> Traceback (most recent call last):
>
> File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 687, in handle
> self.main_loop(options)
>
> File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 731, in main_loop
> while self.controler_socket(): # Unqueue all pending messages
>
> File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 234, in controler_socket
> hostname = u(msg[0])
>
> File "/usr/lib/python3/dist-packages/zmq/utils/strtypes.py", line 34, in cast_unicode
> return s.decode(encoding, errors)
>
> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte
>
> 2019-08-20 09:14:44,467 INFO [CLOSE] Closing the controler socket and dropping messages
> _______________________________________________
> Lava-users mailing list
> Lava-users@lists.lavasoftware.org
> https://lists.lavasoftware.org/mailman/listinfo/lava-users
--
Rémi Duraffort
LAVA Tech Lead
Linaro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lavasoftware.org/pipermail/lava-users/attachments/20191014/d8a74658/attachment-0001.html>
------------------------------
Message: 3
Date: Mon, 14 Oct 2019 15:14:32 +0000
From: Diego Russo <Diego.Russo@arm.com>
To: Remi Duraffort <remi.duraffort@linaro.org>, cnspring2002
<cnspring2002@aliyun.com>
Cc: lava-users <lava-users@lists.lavasoftware.org>
Subject: Re: [Lava-users] repeat in lava not work
Message-ID: <5D14BD31-7473-4FA5-A34C-A59AC55286C1@arm.com>
Content-Type: text/plain; charset="utf-8"
We bumped exactly on the same problem few months back.
Can we have this removed from documentation? Keeping it there confuses people.
Thanks
From: Lava-users <lava-users-bounces@lists.lavasoftware.org> on behalf of Remi Duraffort <remi.duraffort@linaro.org>
Date: Friday, 11 October 2019 at 07:56
To: cnspring2002 <cnspring2002@aliyun.com>
Cc: lava-users <lava-users@lists.lavasoftware.org>
Subject: Re: [Lava-users] repeat in lava not work
Hello,
I do confirm that the repeat block is not working and we are not planning to work on that feature anytime soon.
In fact it has never worked properly.
If you want to repeat actions, just add many actions block. You can use a templating engine like jinja2 to generate the job definition.
Rgds
Le jeu. 10 oct. 2019 à 07:46, cnspring2002 <cnspring2002@aliyun.com<mailto:cnspring2002@aliyun.com>> a écrit :
actions:
- repeat:
count: 2
I just add above in job, and web submit validator told me:
Job submission error: extra keys not allowed @ data['actions'][1]['repeat']
Does it still work now?
_______________________________________________
Lava-users mailing list
Lava-users@lists.lavasoftware.org<mailto:Lava-users@lists.lavasoftware.org>
https://lists.lavasoftware.org/mailman/listinfo/lava-users
--
Rémi Duraffort
LAVA Tech Lead
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lavasoftware.org/pipermail/lava-users/attachments/20191014/e7151caa/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
Lava-users mailing list
Lava-users@lists.lavasoftware.org
https://lists.lavasoftware.org/mailman/listinfo/lava-users
------------------------------
End of Lava-users Digest, Vol 14, Issue 10
******************************************